DOL DevOps Principles 5

Question 1

What is the MAIN risk of having a long-running feature branch that is isolated from the main branch for weeks?

Accepted Answer

It creates large, complex merges and integration conflicts

Answer

Long-lived branches accumulate divergence from the mainline, leading to painful, error-prone merge conflicts when eventually integrated.

Question 2

Which DevOps practice MOST directly reduces the 'mean time to detect' (MTTD) a production issue?

Accepted Answer

Comprehensive real-time monitoring and alerting

Answer

Real-time monitoring and alerting automatically surfaces anomalies as they occur, dramatically reducing the time between failure onset and discovery.

Question 3

A team implements 'dark launches' to test new functionality. What DevOps principle does this support?

Accepted Answer

Testing in production safely without exposing users to risk

Answer

Dark launches run new code paths in production with real data but without exposing output to users, enabling realistic validation with zero customer risk.

Question 4

According to DevOps principles, who should be primarily responsible for defining and enforcing security controls in the pipeline?

Accepted Answer

Security is embedded into the development team (DevSecOps) and automated in the pipeline

Answer

DevSecOps integrates security practices and tooling directly into the CI/CD pipeline, making security a shared team responsibility from day one.

Question 5

What is the CORE purpose of a service level objective (SLO) in a DevOps reliability framework?

Accepted Answer

To set an internal reliability target that balances user expectations with engineering effort

Answer

SLOs define reliability targets (e.g., 99.9% uptime) that guide prioritization between reliability work and new features using error budgets.

(DOL) DevOps Leader Practice Test

(DOL) DevOps Leader Practice Test

DOL DevOps Principles 5