DOL Cloud and Infrastructure Strategy Flashcards

What is the primary purpose of a disaster recovery (DR) plan in a DevOps cloud environment?

Answer: Ensuring systems can be restored within defined RTO and RPO targets after a failure

A DR plan defines recovery time objectives (RTO) and recovery point objectives (RPO) and the procedures to meet them, ensuring business continuity after failures.

A DevOps Leader is implementing chaos engineering. What is the primary goal of this practice?

Answer: Proactively injecting controlled failures to identify weaknesses in system resilience before they cause real outages

Chaos engineering (e.g., Netflix's Chaos Monkey) intentionally introduces failures in a controlled way to discover and fix reliability weaknesses before they occur organically.

Which deployment strategy minimizes risk by routing a small percentage of production traffic to the new version before full rollout?

Answer: Canary deployment

Canary deployments gradually shift traffic to the new version, allowing teams to detect issues with a small blast radius before full rollout.

What is the benefit of using feature flags in a DevOps continuous delivery workflow?

Answer: Decoupling code deployment from feature release, enabling safe testing in production and instant rollback

Feature flags allow teams to ship code to production without activating features, enabling gradual rollouts, A/B testing, and instant disabling without redeployment.

How does observability differ from traditional monitoring in a cloud-native DevOps environment?

Answer: Observability enables understanding of internal system state from external outputs (logs, metrics, traces), while monitoring tracks predefined metrics

Observability uses the three pillars — logs, metrics, and distributed traces — to understand *why* a system behaves a certain way, not just *that* something is wrong.

A DevOps Leader must justify cloud infrastructure spend to executives. Which metric best demonstrates business value?

Answer: Cost per deployed feature or cost per transaction relative to revenue impact

Tying infrastructure cost to business outcomes like cost per transaction or revenue impact makes spend tangible and justifiable to non-technical stakeholders.