Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail company is modernizing its cloud operations by adopting Site Reliability Engineering (SRE) and DevOps principles. Currently, the engineering organization faces two major operational challenges:
Which SRE practices should the company implement to overcome these challenges?
Graceful degradation is an architectural resiliency pattern where a system continues to provide reduced or essential functionality when an underlying component is overloaded or unavailable—for example, serving cached data when a primary database goes offline. Service-level indicators (SLIs) are quantifiable, numerical metrics—such as request latency, error rate, or system availability—used to measure the actual performance and health of a service from the user's perspective.
This option would be the right choice if the company needed to maintain partial application functionality during downstream storage outages and wanted to establish quantifiable numerical metrics to measure user-facing service health and availability.
In Site Reliability Engineering (SRE), SLIs are compared against target SLOs to calculate a service's remaining error budget. When an outage consumes a significant portion of that error budget, it typically triggers a blameless postmortem and prioritizes engineering work to automate toil and improve system resilience.
Distributed tracing is an observability technique that tracks the end-to-end journey of a single user request or transaction as it flows through multiple microservices or application components. It helps engineers pinpoint where performance bottlenecks or component failures occur. A centralized knowledge base is a shared repository of known issues, solutions, and troubleshooting guides that operations teams use to quickly diagnose and resolve recurring technical problems during incident management.
This option would be the right choice if the company needed to identify latency bottlenecks across complex microservices during user transactions and wanted to reduce incident escalation times by giving support engineers a searchable repository of known troubleshooting solutions.
In a mature SRE environment, insights gathered from distributed tracing are often included as factual evidence during a blameless postmortem, and the resulting lessons learned are frequently published into a centralized knowledge base to educate the wider organization.
An incident runbook (or playbook) is a standardized reference guide that documents the specific procedures, communication protocols, escalation paths, and triage steps teams must follow during an active incident. Fault injection testing is a proactive resilience testing practice where engineers deliberately introduce controlled failures—such as network latency, blocked dependencies, or terminated hosts—into a system to verify that it recovers gracefully and triggers expected alerts.
This option would be the right choice if the organization wanted to standardize manual triage and escalation steps during active outages and proactively validate that its cloud architecture can withstand simulated component failures and network disruptions.
SRE teams continuously strive to convert static runbooks into automated remediation scripts to reduce toil. Additionally, action items generated during a blameless postmortem often lead teams to update their runbooks and design new fault injection tests to verify that the fix prevents future outages.
In Site Reliability Engineering (SRE) and DevOps, maintaining system stability while sustaining rapid innovation requires addressing both operational efficiency and organizational culture. Toil refers to manual, repetitive, automatable operational work that lacks enduring value and scales linearly as a service grows. Minimizing toil through automation—such as implementing Infrastructure as Code (IaC) and automated CI/CD pipelines—eliminates routine human intervention. A blameless postmortem (also called a post-incident review) is a structured written record of an incident that analyzes its impact, mitigation steps, and systemic root causes without punishing or blaming individuals.
Unlike purely technical monitoring tools or manual troubleshooting guides, combining toil automation with blameless postmortems directly resolves both the operational bottleneck of manual work and the cultural barrier preventing honest root cause analysis. It aligns development and operations teams around shared reliability goals and continuous improvement.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated