KCNA - Cloud Native Architecture (12% of the exam) - Section 4.1
Describe the defining principles of cloud native architecture.
Immutable infrastructure, declarative configuration, loose coupling, resilience by design, elasticity, and the CNCF definition of cloud native. Also the trade-offs of microservices against a monolith.
A newcomer to cloud native wants a single interactive resource that categorises tools by function, such as monitoring, container runtimes, and databases, and shows which tools are CNCF-hosted along with their maturity levels. Which CNCF resource provides this overview?
AThe Kubernetes Dashboard, a web UI for viewing workloads in one cluster
BArtifact Hub, a place to search for and install Helm charts and other packages
CThe Governing Board charter, a document describing the foundation's membership rules
DThe CNCF Landscape, an interactive map of cloud native tools grouped by categorycheck_circle Correct
Recognise the CNCF Landscape as the interactive map categorising cloud native tools and their maturity levels. The CNCF Landscape exists to help people navigate a crowded ecosystem. It groups projects and products into functional categories and flags CNCF-hosted projects with their maturity, which no cluster UI, package hub, or governance document provides.
Why A is wrong: The Kubernetes Dashboard is a real tool, but it displays resources inside a single cluster rather than mapping the wider ecosystem of cloud native projects.
Why B is wrong: Artifact Hub is a genuine CNCF project for finding packages such as Helm charts, which makes it plausible, but it catalogues installable artifacts rather than categorising the tool landscape by maturity.
Why C is wrong: The charter is a real governance document, but it defines organisational rules and contains no interactive map of cloud native tools or their maturity.
Why D is correct: The CNCF Landscape is the interactive map that organises cloud native tools into categories and marks which are CNCF-hosted along with their maturity, exactly matching the need described.
Answers that look right on this material and are not. Each one is a distractor from a different question in the KCNA bank for this domain.
The Technical Oversight Committee, the body that governs the technical direction of CNCF projects
errorWhy it is wrong: Tempting as an authoritative CNCF source, but the committee governs projects and does not itself serve as a browsable catalogue of ecosystem tools.
Open a shell into each running container and edit the configuration files directly so no redeploy is needed
errorWhy it is wrong: Editing files inside a live container is tempting because it seems faster, but it mutates the running instance in place, which is the mutable pattern immutable infrastructure exists to avoid.
In constants compiled directly into the application source so they travel with the build
errorWhy it is wrong: Hardcoding config as constants feels convenient because it needs no external setup, but twelve-factor explicitly forbids storing per-deploy config in code, since code should be identical across deploys.