Information Technology Foundations for the CL Candidate
What this domain tests
Information Technology asks you to show fluency in the building blocks of a modern IT estate: hardware, software, networks, databases and the people who run them. Questions reward precise vocabulary and a clear grasp of how components interact, not memorised specifications. Expect terms such as client-server and tiered architecture, virtualisation, cloud service models (IaaS, PaaS, SaaS), local and wide area networks, bandwidth versus latency, and the difference between backup and archiving.
Concepts to master
Be comfortable distinguishing system software (operating systems, utilities) from application software, and open-source from proprietary licensing. Understand how data flows from capture through processing to output, and where storage fits: primary memory, secondary storage, and increasingly cloud object storage. Know the roles of servers, endpoints, middleware and APIs. A frequent topic is virtualisation and containers, and why they change capacity planning and licensing.
Traps that appear in questions
- Confusing IaaS with SaaS: the customer manages more in IaaS, less in SaaS.
- Treating bandwidth as speed; latency and throughput are different measures.
- Assuming cloud removes responsibility for data integrity or access control.
- Mixing up backup (operational recovery) with archive (retention).
- Ignoring the human layer: change management and user competence drive outcomes.
Worked example / rule of thumb
A firm moves an email suite to a vendor-hosted service where the vendor manages applications, servers and storage. Ask: who controls the application configuration and data? The customer retains data ownership and user administration, but the vendor runs the platform. That is SaaS, not IaaS. Rule of thumb: locate the management boundary first, then name the model.
Exam technique
When a question describes a scenario, identify the layer (infrastructure, platform, application) before answering. Eliminate options that overstate what technology alone can deliver; governance and process usually sit alongside the tool.