Why is it important for a 12-factor app to start up quickly?

To ensure the app can handle more concurrent requests.

To avoid the need for a load balancer.

To reduce the amount of memory used by the app.

To reduce the time it takes to deploy new releases.

A DevOps engineer is deploying a Python web service to three environments: development, staging, and production. The application code is stored in a single Git repository. The engineer needs to configure the database connection string, API keys for third-party services, and feature flags so they differ per environment. The team wants to avoid committing secrets to the repository and avoid rebuilding the container image for each environment. What is the 12-factor compliant approach?

Create a separate Git branch for each environment, modifying the configuration file in each branch, and deploy from the respective branch.

Store all configuration values in a JSON file in the repository and load it at runtime, overriding values with environment variables when present.

Use a configuration management tool like Ansible to generate a config file on the server at deploy time, and bake the secrets into the container image.

Inject configuration via environment variables at deployment time, reading them in the application code, and keep the same container image across all environments.

Why does a 12-factor app write logs to stdout instead of managing log files?

To make the app independent of the logging infrastructure.

To improve application performance by avoiding disk I/O.

To allow the app to run on servers without a file system.

To ensure logs are stored in a specific format.

Why does the 12-factor app methodology separate configuration from code?

To make the code more readable by removing hardcoded values.

To improve application performance by avoiding file I/O.

To allow the same codebase to be deployed to different environments without code changes.

To reduce the number of environment variables needed.

What is the goal of the 'dev/prod parity' principle in the 12-factor app methodology?

To make development, staging, and production environments as similar as possible.

To keep development and production on separate codebases.

To use different programming languages in development and production.

To make production environment more powerful than development.

CiscoCertified DevNet Professional

Domain 4Objective 5

Describe the Tenets of the "12-Factor App" 350-901 Practice Questions (Page 1)

Part of the 4.0 Application Deployment and Security domain, which accounts for 20% of the 350-901 exam. Cisco does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–16 in this domain), expect 1–1 from this objective — we provide 30 practice questions to prepare you well beyond it. (estimate)

30questions here

6free pages

12concepts

20%of the exam

Questions 1–5

1foundation · easy
Why is it important for a 12-factor app to start up quickly?
Select an answer first
2application · medium
A DevOps engineer is deploying a Python web service to three environments: development, staging, and production. The application code is stored in a single Git repository. The engineer needs to configure the database connection string, API keys for third-party services, and feature flags so they differ per environment. The team wants to avoid committing secrets to the repository and avoid rebuilding the container image for each environment. What is the 12-factor compliant approach?
Select an answer first
3foundation · easy
Why does a 12-factor app write logs to stdout instead of managing log files?
Select an answer first
4foundation · easy
Why does the 12-factor app methodology separate configuration from code?
Select an answer first
5foundation · easy
What is the goal of the 'dev/prod parity' principle in the 12-factor app methodology?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 350-901

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “350-901” is a trademark of its owner, used for identification only.