KCNA Cloud Native Architecture Practice Question
In the 12-factor app methodology, which factor describes the practice of storing configuration in environment variables?
⚠ Common exam trap
CNCF often tests the distinction between 'Config' and 'Backing services'—candidates mistakenly think storing database credentials in environment variables is a 'Backing services' concern, but it is actually a 'Config' concern because the credentials are configuration, not the service itself.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Config
The Config factor (Factor III) of the 12-factor app methodology mandates that configuration—such as database URLs, credentials, or feature flags—be stored in environment variables. This decouples configuration from code, allowing the same build to be deployed across different environments without code changes, and prevents accidental commits of secrets to version control.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Backing services
Why it's wrong here
Backing services concerns treating attached resources such as databases and queues as interchangeable, addressed via configuration; it does not itself define storing configuration in environment variables. It is tempting because backing service credentials are commonly supplied through environment variables.
- ✓
Config
Why this is correct
The Config factor requires configuration to be stored in environment variables rather than committed to code, enabling the same deployment artefact to run across environments. This separation lets operators change settings without rebuilding, exactly as the stem describes.
- ✗
Processes
Why it's wrong here
Processes covers executing the app as stateless processes, not configuration storage. It is tempting because processes do consume injected environment variables at runtime, but the factor mandating config in environment variables is Config, which separates deploy-varying settings from code.
- ✗
Build, release, run
Why it's wrong here
Build, release, run separates code stages into a deployable build, a release combined with config, and execution; it references config but does not prescribe environment variables as its storage. It is tempting because the release stage is where configuration is bound to a build.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.