LFCA Linux Foundation Certified IT Associate Exam Topics and Questions

Linux Fundamentals is the foundation the rest of this exam sits on. At 16%, it is not the heaviest topic, but every other domain assumes you are comfortable here. The two sub-topics, the Linux operating system itself and the command line, work as a pair: understanding what the OS does at a conceptual level only gets you so far if you cannot translate that into the commands that act on it.

How Linux Fundamentals is tested

Items in this topic divide cleanly into two types. The first type checks whether you know what Linux components do: the kernel, the shell, the filesystem hierarchy, permissions, and how processes are managed. The second type is more practical: it gives you a scenario and expects you to know which command, flag, or combination of flags produces a specific result.

The trap candidates fall into is treating command syntax as memorisation rather than logic. Items reward understanding what a command is doing, not recalling a string of characters. When a scenario describes a file permission problem or a process that needs to be killed, the strongest option reflects the right tool for that specific situation, not just any plausible command.

Another common miss is the filesystem hierarchy. Candidates who have used Linux casually often know a few directories but stumble when items probe less familiar paths. Know what lives where and why, and you will cover a disproportionate share of the marks available here.

System Administration Fundamentals carries the largest share of the exam at 30%, and the breadth of its five sub-topics explains why. Where Linux Fundamentals asked you to know the tools, this topic asks you to operate a live system: configure it, keep it running, connect it to a network, diagnose it when something breaks, and recover it when something breaks badly. Expect more than a quarter of your exam to come from here.

– Day-to-day administration and best practices

System administration at this level covers the decisions a sysadmin makes repeatedly: managing users and groups, controlling access, scheduling jobs, handling logs, and keeping packages up to date. Best practices questions are not about opinion; they test whether you know the accepted approach for a given situation. That means knowing why you use the principle of least privilege when assigning permissions, why you avoid running services as root, and why configuration changes belong in version-controlled files rather than edited in place. Items in this area reward the candidate who can distinguish between what works and what is recommended.

– Networking in a Linux environment

The networking sub-topic focuses on what a sysadmin configures and verifies, not on deep protocol theory. You need to be comfortable with IP addressing, DNS resolution, and the tools used to inspect and troubleshoot network interfaces on a Linux host. Know how to check connectivity, read interface configuration, and understand what a routing table tells you. Items here often give you a symptom and ask you to identify either the cause or the next diagnostic step. The candidate who treats networking as someone else's problem will lose marks on questions that look like general sysadmin scenarios but turn on a network configuration detail.

– Troubleshooting and disaster recovery

Troubleshooting questions follow a pattern: a system is misbehaving and you are given context, usually a log snippet, an error message, or a description of symptoms, and asked to identify what is wrong or what to do next. Items reward a methodical approach. Guessing at the most dramatic fix rarely wins; isolating the layer where the fault sits does.

Disaster recovery shifts the frame from fixing a running system to restoring one that has failed. Know the difference between a backup strategy and a recovery strategy: having backups is not the same as being able to restore from them under pressure. Items test whether you understand recovery time objectives, backup types, and the steps taken in the right order when a system needs to be brought back. This is where candidates who have only read about these concepts, and never thought through the sequence, drop marks.

How System Administration Fundamentals is tested

At 30% of the exam, this topic alone can determine whether you pass. Items are almost always scenario-based: a described environment, a described problem or goal, and four options that all look plausible to a candidate who has partial knowledge.

The most common trap is choosing an action that addresses the symptom rather than the cause. Items reward candidates who read the scenario carefully enough to identify the actual fault before selecting an action. A second common trap appears in best-practices questions: two options both work, but only one reflects the recommended approach for a production environment.

Disaster recovery items are particularly unforgiving. They often hinge on sequence: doing the right things in the wrong order is tested as a wrong answer. Networking items tend to test diagnostic reasoning rather than protocol detail, so the candidate who can read a scenario and name the right tool earns the mark, while the candidate who knows the tool but misreads the scenario does not.

After the depth of system administration, Cloud Computing Fundamentals shifts you to a different operating model. At 18%, it is the second-heaviest topic. The five sub-topics span concepts, economics, and operations: understanding what cloud computing is, keeping services available and performant, controlling costs, following accepted practice, and managing cloud networking. The exam treats cloud as a working environment, not a marketing category.

– Cloud concepts and networking

The cloud computing sub-topic covers the foundational model: service types, deployment models, and the shared responsibility model. The examinable part of the shared responsibility model is knowing where the provider's obligations end and the customer's begin, because that boundary shifts depending on whether you are using infrastructure, platform, or software as a service. Cloud networking adds virtual networks, subnets, security groups, and load balancers to the picture. Items here test whether you can read a described architecture and identify which networking component is responsible for a given behaviour. Candidates who treat cloud networking as identical to on-premises networking will misread scenarios where the cloud model changes the answer.

– Availability, performance, budgeting, and best practices

Performance and availability questions ask you to reason about redundancy, scaling, and fault tolerance in cloud environments. Know the difference between scaling horizontally and vertically, and know which problems each approach addresses. Availability targets matter here: the concept of a service level agreement and what affects it will appear.

Budgeting is an area candidates underestimate. Cloud cost management is a discipline with specific tools and strategies: reserved capacity versus on-demand pricing, cost allocation by tag, and identifying idle resources. Items reward candidates who understand that cost decisions are architectural decisions.

Best practices questions in this topic tend to test security hygiene in cloud environments: least-privilege IAM policies, avoiding hardcoded credentials, encrypting data at rest and in transit. These overlap with the Security Fundamentals topic, but the cloud framing changes the specific controls that apply.

How Cloud Computing Fundamentals is tested

At 18%, this topic contributes meaningfully to your score, and the five sub-topics mean items can come from several different directions. Scenario items in this topic often describe a business requirement and ask which cloud approach satisfies it. The trap is choosing an option that is technically correct in isolation but wrong for the described constraint, whether that constraint is cost, availability, or compliance.

Budgeting items are a common surprise for candidates with a technical background. They are not asking you to calculate a bill; they reward understanding which architectural choices drive cost up or down and which tools surface that information.

Networking items tend to be the most specific: a described connectivity problem in a virtual network environment where the answer turns on which component, a security group rule, a routing table entry, a subnet configuration, is misconfigured. Candidates who can map symptoms to the responsible layer earn these marks. Candidates who guess at the most visible component often do not.

Security Fundamentals sits at 14% and covers three sub-topics: security principles and controls, handling sensitive data, and compliance. The topic is narrower than System Administration but demands precision. Security items are often written so that two options are both defensible in general terms: the mark goes to the candidate who knows the specific control, classification, or requirement that applies in the described situation.

How Security Fundamentals is tested

Security items on this exam test applied judgement, not definitions. The security sub-topic produces scenarios where you need to identify the right control for a described threat or the right response to a described incident. Items reward the candidate who can match a control to a threat model, not the one who can recite a list of control types.

Sensitive data questions hinge on classification and handling. The examinable point is knowing what obligations attach to different categories of data and what constitutes a handling failure. Compliance questions extend this: they test whether you understand why a requirement exists well enough to apply it to a situation you have not seen before.

The most common place candidates lose marks is in treating security as a set of independent facts rather than a connected set of obligations. An item that describes a data handling scenario may be testing a compliance requirement; an item that looks like a compliance question may turn on a technical control. Read the scenario for what it is actually asking before selecting an option.

DevOps Fundamentals accounts for 12% of the exam and covers three sub-topics: the basics of DevOps as a working approach, Git as a version control system, and containers. For many candidates sitting the Linux Foundation Certified IT Associate, this topic covers ground that feels adjacent to their daily work but slightly outside it. The exam tests whether you understand these tools well enough to work alongside the people who use them every day.

How DevOps Fundamentals is tested

DevOps Basics questions test the concepts that underpin continuous integration and continuous delivery: why automation reduces deployment risk, what a pipeline does, and how DevOps practices change the relationship between development and operations. Items reward understanding the rationale behind a practice, not just its name.

Git questions are the most specific in this topic. The exam expects you to know the core workflow: initialising a repository, staging and committing changes, branching, merging, and resolving the situations that arise when those operations conflict. Items tend to describe a state of a repository and ask what action produces a described outcome. Candidates who know Git commands but have not thought through what each one does to the repository state will find these items harder than expected.

Container questions focus on what containers are, how they differ from virtual machines, and how they are managed at a basic level. The depth expected is conceptual and operational, not administrative. Losing marks here is usually a sign that a candidate skipped containers as too technical, when the items are actually testing whether you can read a described containerised environment and reason about it.

IT Project Management Fundamentals is the final topic and the lightest at 10%. Its four sub-topics span project management methodology, software application architecture, functional analysis, and open source licensing. Candidates with a technical background sometimes underestimate this topic because it looks soft compared to system administration or security. The licensing sub-topic in particular contains precise, examinable distinctions that punish guessing.

– Project management and functional analysis

Project management questions at this level test whether you understand the phases of a project, how requirements are gathered and managed, and how scope, time, and cost interact. You do not need deep knowledge of a specific methodology, but you do need to know the difference between waterfall and agile approaches well enough to identify which fits a described situation. Functional analysis is closely related: it covers how business requirements are translated into system requirements. Items here reward candidates who can read a described stakeholder need and identify what kind of analysis or documentation addresses it. The trap is choosing an answer that sounds managerial rather than one that reflects what the analysis step actually produces.

– Software architecture and open source licensing

Software application architecture questions test familiarity with common architectural patterns: monolithic versus microservices, client-server models, and the trade-offs each involves. Items do not expect you to design a system; they expect you to read a described architecture and identify its characteristics or limitations.

Open source licensing is the most precise sub-topic in this topic. The distinctions between permissive and copyleft licences are directly examinable, and the exam tests whether you know what obligations a given licence type imposes on someone who distributes modified code. Candidates who treat all open source as freely usable without conditions will lose marks. Know the practical difference between what a permissive licence allows and what a copyleft licence requires, because items are written around exactly that boundary.

How IT Project Management Fundamentals is tested

At 10%, this topic contributes the smallest share of marks, but it covers four distinct sub-topics, which means items can arrive from very different directions. Candidates who leave it under-prepared because it looks straightforward often drop marks they could have kept with an hour of focused review.

Project management and functional analysis items tend to be scenario-based: a described project situation where you select the appropriate action or document. Items reward knowing the purpose of a step, not its name. Architecture items follow a similar pattern: a described system with a described problem, and you identify which architectural characteristic is responsible.

Licensing items are the most fact-dependent in this topic. They reward candidates who know what specific licence types require, particularly around distribution and modification. These items do not respond well to reasoning from general principles: you either know what a copyleft licence obligates a distributor to do, or you guess. A small amount of focused preparation on this sub-topic returns a disproportionate number of marks relative to the time spent.