LFCA: IT and operational foundations
Prepare for LFCA with seven lessons, 35 questions, and five cases on Linux, administration, cloud, security, DevOps, and IT project management.
Objectives and progression
Seven lessons, 35 questions, and five original scenarios with fictional banking and APS examples. Internal assessment of 26 decisions in 50 minutes, distinct from the official exam. Initial six-domain coverage without executable labs or assurance of complete readiness. LFCA competencies updated 2025-09-16, confirmed 2026-09-30. Weights: Linux 16%, administration 30%, cloud 18%, security 14%, DevOps 12%, and IT project management 10%. Official exam: 60 questions, 90 minutes, 75% passing score, English. LFCA-JP retired.
Audience: Professionals starting IT, cloud, support, and technical coordination roles.
Prerequisites: No prior certification required. Basic computer familiarity and practice in an isolated Linux environment support study.
315 estimated study minutes
- Interpret the environment and command effects before execution.
- Diagnose service state, usage, and permissions through scoped evidence.
- Follow communication paths and translate continuity into verifiable objectives.
- Choose cloud models and controls according to operations, resilience, and budget.
- Limit access and manage secrets and data throughout their lifecycle.
- Connect traceability, validation, and persistence to delivery flow.
- Translate business goals into technical decisions and delivery criteria.
Modules
- Linux, shell, and permissions
- Services, logs, and capacity
- Networking and recovery
- Cloud, responsibility, and cost
- Security, identities, and data
- DevOps, Git, and containers
- Requirements, architecture, and acceptance
Continue learning
References and version
LFCA domains and competencies updated2025-09-16; current page confirmed2026-09-30
- Linux Foundation Certified IT Associate · 2026-09-30
- LFCA program changes effective September16,2025 · 2026-09-30
- Multiple-choice exam instructions · 2026-09-30
- Multiple-choice exam FAQ and score · 2026-09-30
- Exam language availability · 2026-09-30
- Bash shell manual · 2026-09-30
- GNU chmod permissions · 2026-09-30
- Linux pathname resolution · 2026-09-30
- Operating-system identification · 2026-09-30
- systemctl service lifecycle · 2026-09-30
- journalctl log filtering · 2026-09-30
- GNU df space and inodes · 2026-09-30
- GNU du directory usage · 2026-09-30
- Linux routing · 2026-09-30
- Socket inspection · 2026-09-30
- Name Service Switch lookup · 2026-09-30
- NIST definition of cloud computing · 2026-09-30
- Cloud shared responsibility · 2026-09-30
- AWS Budgets cost monitoring · 2026-09-30
- Budget actions require configuration · 2026-09-30
- Regions and Availability Zones · 2026-09-30
- Disaster recovery strategies · 2026-09-30
- Contingency planning and recovery objectives · 2026-09-30
- Digital identity authentication guidance · 2026-09-30
- Git revert · 2026-09-30
- Git ignore and tracked files · 2026-09-30
- Container fundamentals · 2026-09-30
- Persistent container volumes · 2026-09-30
- Reliable product launches · 2026-09-30
- Microservice architecture tradeoffs · 2026-09-30
- Open Source Definition · 2026-09-30
- Image build and tag references · 2026-09-30
- Logging data and access protection · 2026-09-30
- IAM least privilege and credential lifecycle · 2026-09-30
- NIST cloud models and elasticity · 2026-09-30
- NIST recovery objectives and exercises · 2026-09-30
- Immutable image digests · 2026-09-30
What you will explore
0 / 7Linux, shell, and permissions
Interpret the environment and command effects before execution.
Services, logs, and capacity
Diagnose service state, usage, and permissions through scoped evidence.
Networking and recovery
Follow communication paths and translate continuity into verifiable objectives.
Cloud, responsibility, and cost
Choose cloud models and controls according to operations, resilience, and budget.
Security, identities, and data
Limit access and manage secrets and data throughout their lifecycle.
DevOps, Git, and containers
Connect traceability, validation, and persistence to delivery flow.
Requirements, architecture, and acceptance
Translate business goals into technical decisions and delivery criteria.