I85PREP
⌘ K
EXIN DevOps Professional study materials
EXIN DevOps Professional study resources

EXIN DevOps Professional practice questions

One question at a time. Build your EXIN DevOps Professional understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1DevOps Practices (Flow, Feedback, Continual Learning)

In the DevOps Three Ways, what does the First Way (Flow) primarily emphasize?

  1. Optimizing the entire value stream from development to operations by reducing batch sizes and work in progress Correct answer.
  2. Maximizing individual team utilization so that every specialist is fully busy
  3. Creating fast automated feedback loops from operations back to development
  4. Establishing a blameless postmortem culture that encourages experimentation

Explanation

The First Way is about the flow of work from Development to Operations and then to the customer. It calls for optimizing the whole system, not local silos, by limiting work in progress, reducing batch sizes, and removing constraints. Feedback loops and learning culture belong to the Second and Third Ways.

Question 2DevOps Practices (Flow, Feedback, Continual Learning)

A team deploys a large batch of fifty merged changes at once and the release fails. Which DevOps practice most directly addresses this by limiting the amount of work in process?

  1. Adding more manual testers to the release approval stage
  2. Assigning a dedicated release manager to coordinate the batch
  3. Reducing batch size and deploying smaller, more frequent changes Correct answer.
  4. Increasing the number of approval gates before deployment

Explanation

Small batch sizes shorten lead time, reduce variability, and make failures easier to isolate and fix. The First Way explicitly recommends reducing batch size and work in progress to improve flow. Additional gates, testers, or coordinators add handoffs and queue time without shrinking the change itself.

Question 3DevOps Practices (Flow, Feedback, Continual Learning)

Which metric best measures the Second Way principle of fast feedback from operations to development?

  1. The percentage of code covered by unit tests
  2. The mean time to detect and report a production failure back to the team Correct answer.
  3. The total number of deployments performed per quarter
  4. The number of story points completed per sprint

Explanation

The Second Way is about amplifying feedback loops so that problems are detected and communicated quickly. Mean time to detect and report a failure measures how fast operations signals reach development. Story points, unit-test coverage, and deployment counts describe throughput or quality activity but not feedback latency.

Question 4DevOps Practices (Flow, Feedback, Continual Learning)

What is the primary purpose of a blameless postmortem in a DevOps continual learning culture?

  1. To understand contributing causes and share lessons that improve the system Correct answer.
  2. To justify additional change approval board meetings
  3. To determine which individual engineer should be disciplined for the outage
  4. To document the incident for legal compliance only

Explanation

Blameless postmortems focus on systemic causes rather than individual fault, so people share accurate information. The output is shared learning and concrete improvements to the system. Punishment, extra approvals, and compliance-only records undermine openness and do not improve safety.

Question 5DevOps Practices (Flow, Feedback, Continual Learning)

A value stream map shows that code waits nine days for a manual security review while actual review work takes two hours. Which flow improvement should be prioritized?

  1. Increase the review batch size so reviewers handle more code at once
  2. Ask developers to work faster to shorten the two-hour review
  3. Automate the security checks so review happens continuously within the pipeline Correct answer.
  4. Add a second manual review step to catch more issues

Explanation

The map reveals that queue time dominates the lead time, not the review effort itself. Automating security checks moves the constraint into the pipeline and removes the wait. Speeding up a two-hour task, adding steps, or enlarging batches does not address the nine-day queue.

Question 6DevOps Practices (Flow, Feedback, Continual Learning)

Which practice most directly creates a fast feedback loop on code quality before changes reach production?

  1. Quarterly architecture review board meetings
  2. Monthly release notes distributed to stakeholders
  3. Continuous integration that runs automated tests on every commit Correct answer.
  4. Annual penetration testing by an external vendor

Explanation

Continuous integration runs automated builds and tests on every commit, giving developers feedback within minutes. This shortens the loop between introducing and detecting a defect. Quarterly reviews, annual testing, and monthly notes operate on cycles far too slow to provide timely feedback.

Question 7DevOps Practices (Flow, Feedback, Continual Learning)

A team uses feature flags to deploy incomplete work to production without exposing it to users. Which flow benefit does this primarily provide?

  1. It eliminates the need for automated testing
  2. It allows small, frequent integration while decoupling release from deployment Correct answer.
  3. It guarantees that no production incident can occur
  4. It removes the need for a version control system

Explanation

Feature flags decouple deployment from release, so small changes can be integrated and deployed continuously while exposure is controlled. This supports the First Way by keeping batch sizes small. They do not replace testing or version control and cannot guarantee incident-free production.

Question 8DevOps Practices (Flow, Feedback, Continual Learning)

Which organizational change best supports the Third Way of continual learning and experimentation?

  1. Requiring every experiment to be approved by a central change board
  2. Allocating a fixed percentage of engineering time to improvement experiments Correct answer.
  3. Punishing teams publicly when a canary deployment is rolled back
  4. Measuring teams only on individual output volume

Explanation

The Third Way requires a culture that allocates time and safety for experimentation and learning. Dedicating a share of engineering time to improvement work institutionalizes this. Central approval, output-only metrics, and public punishment discourage the risk-taking that learning depends on.

Question 9DevOps Practices (Flow, Feedback, Continual Learning)

During a canary deployment, automated monitoring detects an elevated error rate and rolls back the release without human intervention. Which feedback mechanism does this illustrate?

  1. A quarterly business review
  2. A static code analysis gate at commit time
  3. An automated production feedback loop that shortens time to remediate Correct answer.
  4. A manual change advisory board decision

Explanation

Automated monitoring of a canary and automatic rollback is a production feedback loop that detects and corrects problems quickly. It shortens the time between fault and remediation and reduces blast radius. Change boards, business reviews, and commit-time analysis operate at different points and speeds.

Question 10DevOps Practices (Flow, Feedback, Continual Learning)

What is the main flow-related reason for limiting work in progress (WIP) in a DevOps value stream?

  1. It reduces queueing and shortens lead time through the system Correct answer.
  2. It allows larger batches to be processed more efficiently
  3. It increases the number of approvals required per change
  4. It guarantees that every engineer is fully utilized

Explanation

Limiting WIP reduces the number of items waiting in queues, which shortens lead time and exposes bottlenecks. This is a core application of the First Way. High utilization, more approvals, and larger batches all increase queueing and work against flow.

Question 11DevOps Practices (Flow, Feedback, Continual Learning)

A production incident is resolved, and the team wants to convert the event into organizational learning. Which action best follows the Third Way?

  1. Raise the change approval threshold for all future deployments
  2. Hold a blameless review, record contributing causes, and assign follow-up improvements Correct answer.
  3. Close the ticket immediately to keep the metrics clean
  4. Add the responsible engineer to a performance improvement plan

Explanation

The Third Way turns incidents into learning by reviewing causes without blame and acting on the findings. Assigning concrete follow-up improvements ensures the learning changes the system. Closing tickets, punishing individuals, or raising approval thresholds does not generate or apply knowledge.

Question 12DevOps Practices (Flow, Feedback, Continual Learning)

Which pair of metrics best reflects the flow of changes through the delivery pipeline?

  1. Deployment frequency and lead time for changes Correct answer.
  2. Number of approvals and size of the change board
  3. Lines of code written and number of meetings attended
  4. Employee utilization and overtime hours

Explanation

Deployment frequency and lead time for changes measure how quickly and often work moves from commit to production. They are core flow metrics in DevOps. Activity counts, approval counts, and utilization do not measure the movement of changes through the value stream.

Question 13DevOps Practices (Flow, Feedback, Continual Learning)

An organization wants to amplify feedback from customers into development. Which practice most directly achieves this?

  1. Requiring customers to submit change requests through a quarterly committee
  2. Instrumenting production usage and error telemetry and reviewing it with developers Correct answer.
  3. Freezing the release schedule to reduce customer-visible changes
  4. Removing monitoring to reduce operational noise

Explanation

The Second Way pushes fast feedback from the customer and operations back to development. Production telemetry on usage and errors, reviewed jointly, gives developers direct and timely signals. Quarterly committees, release freezes, and removing monitoring all slow or block that feedback.

Question 14DevOps Practices (Flow, Feedback, Continual Learning)

What does the DevOps concept of 'paving the road' refer to in the context of flow?

  1. Providing self-service, automated platforms that make the right way the easy way Correct answer.
  2. Outsourcing all operational work to a separate department
  3. Mandating that all teams use the same programming language
  4. Requiring manual infrastructure provisioning tickets for control

Explanation

Paving the road means building shared, self-service platforms and automated pathways so teams can deliver safely without friction. It improves flow by removing handoffs and manual steps. Forced uniformity, manual tickets, and outsourcing create delays and reduce developer autonomy.

Question 15DevOps Practices (Flow, Feedback, Continual Learning)

A team wants to make experimentation safe in production. Which combination best supports this?

  1. Single shared production environment with no monitoring
  2. Feature flags, canary releases, and automated rollback Correct answer.
  3. Removing automated tests to speed up deployment
  4. Longer approval cycles and larger release batches

Explanation

Feature flags, canary releases, and automated rollback limit blast radius and allow fast reversal, making experiments safe. These mechanisms embody the Third Way's experimentation principle combined with Second Way feedback. Slow approvals, larger batches, missing tests, and no monitoring all increase risk.

Question 16DevOps Practices (Flow, Feedback, Continual Learning)

Which statement best explains why handoffs between development and operations degrade flow?

  1. Handoffs increase queue time and lose context, slowing delivery and obscuring feedback Correct answer.
  2. Handoffs reduce the number of approvals required
  3. Handoffs eliminate the need for automation
  4. Handoffs guarantee that specialists remain fully utilized

Explanation

Each handoff creates a queue and a transfer of tacit knowledge that is easily lost. The result is longer lead time and weaker feedback between the people who build and those who run the system. Utilization, automation, and approval counts are not benefits of handoffs.

Question 17DevOps Practices (Flow, Feedback, Continual Learning)

Which practice best embodies the Second Way principle of 'swarming' and stopping the line when a problem is found?

  1. Halting the pipeline on a failed test and fixing it before proceeding Correct answer.
  2. Allowing defects to accumulate until a scheduled stabilization sprint
  3. Lowering test thresholds so the pipeline stays green
  4. Routing failures to a separate team for later triage

Explanation

Stopping the line means the team addresses a failure immediately rather than passing it downstream. Halting the pipeline and fixing the failure keeps feedback short and prevents defect accumulation. Deferring defects, routing them away, or weakening thresholds all extend feedback loops.

Question 18DevOps Practices (Flow, Feedback, Continual Learning)

What is the primary role of telemetry and observability in the DevOps feedback loop?

  1. To document compliance evidence for auditors only
  2. To replace the need for automated testing
  3. To provide real-time signals about system behavior so issues are detected and understood quickly Correct answer.
  4. To increase the number of manual approvals in the release process

Explanation

Telemetry and observability supply the production signals that close the loop between operations and development. They let teams detect, localize, and understand issues quickly. They complement rather than replace testing, and their purpose is operational insight, not approvals or audit-only records.

Question 19DevOps Practices (Flow, Feedback, Continual Learning)

A team's deployment pipeline includes automated performance tests that fail the build when latency exceeds a threshold. Which feedback principle does this implement?

  1. Deferring performance validation to a post-release review
  2. Measuring performance only during annual load tests
  3. Shifting performance feedback left so issues are found before production Correct answer.
  4. Removing performance thresholds to avoid false alarms

Explanation

Running performance tests in the pipeline shifts feedback left, so latency regressions are caught before release. This shortens the loop between introducing and detecting a performance problem. Post-release reviews, removed thresholds, and annual tests all delay or weaken that feedback.

Question 20DevOps Practices (Flow, Feedback, Continual Learning)

Which behavior most clearly indicates a generative, learning-oriented culture in a DevOps organization?

  1. Change approvals are centralized to prevent any deviation
  2. Leaders share their own mistakes and reward teams that surface problems early Correct answer.
  3. Teams hide failures to protect their performance ratings
  4. Managers track and publish individual error counts

Explanation

A generative culture is characterized by high cooperation, shared risk-taking, and leaders who model openness about failure. Rewarding early problem disclosure reinforces learning. Publishing error counts, hiding failures, and centralizing approvals all suppress the information flow learning depends on.

Question 21DevOps Practices (Flow, Feedback, Continual Learning)

What is the main flow benefit of trunk-based development with short-lived branches?

  1. It allows developers to work in isolation for months
  2. It removes the need for automated testing
  3. It reduces merge conflicts and integration delay by keeping changes small and frequent Correct answer.
  4. It eliminates the need for code review

Explanation

Trunk-based development with short-lived branches keeps changes small and integrates them frequently, reducing long-lived divergence and merge pain. This supports fast flow and continuous integration. It does not remove code review or testing, and long isolation is its opposite.

Question 22DevOps Practices (Flow, Feedback, Continual Learning)

An organization measures mean time to restore (MTTR) and finds it high. Which DevOps improvement most directly reduces MTTR?

  1. Practicing automated rollback and rehearsed incident response Correct answer.
  2. Adding more layers of management to the escalation path
  3. Increasing the number of manual approval steps for hotfixes
  4. Extending the change freeze window

Explanation

MTTR measures how quickly service is restored after an incident. Automated rollback and rehearsed response shorten detection-to-recovery time. More approvals, longer freezes, and deeper escalation paths add delay and increase MTTR rather than reduce it.

Question 23DevOps Practices (Flow, Feedback, Continual Learning)

Which statement best captures the relationship between the Three Ways in DevOps?

  1. Feedback is only relevant after continual learning has been fully institutionalized
  2. Continual learning must be completed before any flow improvement can begin
  3. Flow is the foundation, feedback accelerates and safeguards flow, and continual learning sustains both Correct answer.
  4. Flow, feedback, and continual learning are independent initiatives that should be run separately

Explanation

The Three Ways build on each other: flow moves work quickly, feedback shortens the loop to detect and correct problems, and continual learning embeds the culture and practices that sustain improvement. They are interdependent rather than sequential prerequisites or isolated programs.

Question 24DevOps Practices (Flow, Feedback, Continual Learning)

A team automates a manual approval step to speed up delivery, but incident rates rise because risky changes now bypass review. Which DevOps response best addresses the underlying issue?

  1. Reinstate the manual approval step for all changes
  2. Replace the manual gate with automated risk-based checks and progressive delivery Correct answer.
  3. Remove monitoring to reduce the number of reported incidents
  4. Stop all deployments until the incident rate returns to zero

Explanation

The problem is not automation but the loss of risk control. Automated risk-based checks and progressive delivery preserve safety while keeping flow fast. Restoring manual gates reintroduces delay, a full deployment freeze halts value delivery, and removing monitoring hides the problem.

Question 25DevOps Practices (Flow, Feedback, Continual Learning)

Which scenario best demonstrates the Third Way principle of 'repetition and practice'?

  1. Teams run game days and rehearse failure recovery regularly Correct answer.
  2. Teams avoid simulating failures to prevent unnecessary alarm
  3. Teams document recovery procedures once and never review them
  4. Teams rely on individual memory during incidents

Explanation

Repetition and practice means rehearsing skills and failure scenarios so that response becomes reliable under stress. Game days and regular recovery drills embody this. One-time documentation, reliance on memory, and avoiding simulation leave response untested.

Question 26DevOps Practices (Flow, Feedback, Continual Learning)

In the DevOps Three Ways, which outcome is the primary target of the First Way (flow of work from Development to Operations)?

  1. Increasing the number of approval gates per release
  2. Reducing the number of automated tests to speed builds
  3. Maximizing individual utilization rates in each silo
  4. Shortening the lead time from commit to customer value Correct answer.

Explanation

The First Way focuses on the left-to-right flow of work, so its headline outcome is reducing the time a change takes to reach the customer. Utilization of individual silos is a local metric that often harms global flow. Approval gates and fewer tests are not goals of flow; they usually slow it.

Question 27DevOps Practices (Flow, Feedback, Continual Learning)

A value stream map shows that a change spends 4 days waiting for environment availability and 2 hours in actual build and test work. Which conclusion follows most directly?

  1. Test automation should be reduced to shorten the map
  2. The build stage is the bottleneck and needs more compute
  3. The process is already lean because work time is small
  4. The queue time dominates, so environment availability is the constraint to fix Correct answer.

Explanation

Lead time is mostly queue time here, so the constraint is the wait for environments rather than the work itself. Improving the small work portion yields little overall gain. The correct flow response is to remove the waiting, for example with self-service environments.

Question 28DevOps Practices (Flow, Feedback, Continual Learning)

Which practice gives developers fast, self-service access to production-like environments without filing tickets to a separate team?

  1. A spreadsheet tracking which team owns each server
  2. A weekly change advisory board for environment requests
  3. Manual configuration of shared staging servers by operations
  4. Environment provisioning as code with automated pipelines Correct answer.

Explanation

Treating environment creation as code executed by a pipeline lets developers provision on demand, removing the handoff and queue that slow flow. Manual or committee-based allocation reintroduces waiting. Shared manually configured servers also drift and create contention.

Question 29DevOps Practices (Flow, Feedback, Continual Learning)

A team replaces a manual sign-off with automated policy checks in the deployment pipeline. Which feedback characteristic does this change most improve?

  1. The feedback is removed entirely from the release process
  2. The feedback arrives sooner and is applied consistently Correct answer.
  3. The feedback arrives later but is more thorough
  4. The feedback becomes dependent on the reviewer's availability

Explanation

Automated policy checks run on every change within the pipeline, so results return in minutes and apply identical rules each time. This shortens the feedback loop and removes variance from human availability. It does not eliminate control; it relocates control into code.

Question 30DevOps Practices (Flow, Feedback, Continual Learning)

Which measure best quantifies how quickly a team can turn a production failure into a restored service?

  1. Mean time to restore service Correct answer.
  2. Deployment frequency
  3. Change lead time
  4. Change fail percentage

Explanation

Mean time to restore measures elapsed time from failure detection to service recovery, which is the feedback-and-recovery dimension of performance. Lead time and deployment frequency describe flow, and change fail percentage describes stability of changes.

Question 31DevOps Practices (Flow, Feedback, Continual Learning)

A team wants to detect degrading user experience before customers file tickets. Which capability contributes most directly?

  1. A stricter code review checklist
  2. Synthetic and real-user monitoring wired into alerting Correct answer.
  3. Quarterly customer satisfaction surveys
  4. A larger manual regression test suite run nightly

Explanation

Synthetic checks and real-user monitoring observe the running system continuously and can alert on degradation as it happens. That is the fastest signal available before users complain. Nightly suites, surveys, and review checklists operate on much slower cycles.

Question 32DevOps Practices (Flow, Feedback, Continual Learning)

During a post-incident review, a facilitator asks 'what in our system allowed this mistake to cause an outage?' rather than 'who made the mistake?' Which cultural principle does this reflect?

  1. Individual accountability through disciplinary review
  2. Root cause assigned to the last person to touch the system
  3. Change advisory board escalation
  4. Blameless postmortems focused on systemic causes Correct answer.

Explanation

Blameless postmortems assume people act reasonably given the information and tools available, so learning focuses on system design, safeguards, and detection. Blame suppresses reporting and hides the conditions that made the error consequential. The question deliberately redirects attention from persons to systems.

Question 33DevOps Practices (Flow, Feedback, Continual Learning)

Which practice gives a team the fastest signal that a code change has broken a previously working behavior?

  1. A manual smoke test performed before each quarterly release
  2. A wiki page documenting expected behavior
  3. A comprehensive automated test suite executed on every commit Correct answer.
  4. A monthly quality audit by an external assessor

Explanation

Tests that run automatically on every commit detect regressions within minutes of the change, when the author still has full context. Slower or manual checks leave broken behavior in place for long periods. Documentation describes intent but verifies nothing.

Question 34DevOps Practices (Flow, Feedback, Continual Learning)

An organization wants learning from incidents to persist beyond the individuals involved. Which action best achieves this?

  1. Storing postmortem findings in a searchable knowledge base and updating runbooks and tests Correct answer.
  2. Relying on the memory of senior engineers who handled past incidents
  3. Restricting incident details to the on-call rotation
  4. Closing incidents quickly to keep the ticket queue short

Explanation

Continual learning requires that knowledge be externalized into artifacts the whole organization can reuse, such as searchable postmortems, updated runbooks, and regression tests. Otherwise the lesson leaves when the person leaves. Restricting or rushing incident handling prevents that transfer.

Question 35DevOps Practices (Flow, Feedback, Continual Learning)

Which practice most directly shortens the feedback loop between a hypothesis about user behavior and evidence about it?

  1. Increasing the size of each release batch
  2. Holding a biannual roadmap planning offsite
  3. Running controlled experiments with feature flags and measuring outcomes Correct answer.
  4. Requiring sign-off from three stakeholders before any experiment

Explanation

Controlled experiments behind feature flags let teams expose a change to a subset of users and measure the effect quickly, closing the loop between hypothesis and evidence. Larger batches and heavy sign-off slow the cycle, and planning offsites do not generate user evidence.

Question 36DevOps Practices (Flow, Feedback, Continual Learning)

A team holds regular game days in which engineers practice responding to simulated outages in a production-like environment. Which purpose does this serve?

  1. It replaces the need for monitoring and alerting
  2. It rehearses response skills and surfaces weaknesses before real incidents occur Correct answer.
  3. It satisfies an audit requirement for documented procedures
  4. It transfers responsibility for reliability to a single specialist

Explanation

Game days build the muscle memory of incident response and reveal gaps in tooling, runbooks, and coordination under safe conditions. They complement monitoring rather than replace it, and they distribute rather than concentrate operational skill.

Question 37DevOps Practices (Flow, Feedback, Continual Learning)

A team wants to reduce batch size in its delivery process. Which change is most consistent with that goal?

  1. Merging many features into one large release to reduce release overhead
  2. Combining all database migrations into a single annual deployment
  3. Delivering small, independently deployable changes frequently Correct answer.
  4. Accumulating changes on a long-lived release branch

Explanation

Small, independently deployable changes keep batch size low, which shortens feedback and limits the blast radius of any failure. Consolidating work into larger units increases risk and delays learning. Release overhead is better attacked through automation than through bigger batches.

Question 38DevOps Practices (Flow, Feedback, Continual Learning)

Which statement best describes the role of a deployment pipeline in the feedback loop?

  1. It documents the release process for auditors
  2. It guarantees that no defective change can ever reach production
  3. It provides staged, automated verification that returns results to the author quickly Correct answer.
  4. It replaces the need for production monitoring

Explanation

A pipeline runs successive automated checks on each change and reports results back fast, so defects are caught close to their introduction. It cannot guarantee zero defects and does not replace observing the running system. Its purpose is fast verification, not documentation.

Question 39DevOps Practices (Flow, Feedback, Continual Learning)

A team's dashboards show deployment frequency rising while change fail percentage also rises sharply. What does this pattern most likely indicate?

  1. The rise in failures proves that frequent deployment is harmful
  2. The metrics are unrelated and should be ignored
  3. The team should stop measuring deployment frequency
  4. Flow improved but the feedback controls that catch defects are too weak Correct answer.

Explanation

High throughput paired with rising failure rate suggests the team is pushing changes faster than its verification and monitoring can catch problems. The response is to strengthen automated testing, observability, and progressive delivery, not to abandon frequent deployment. The two metrics must be read together.

Question 40DevOps Practices (Flow, Feedback, Continual Learning)

Which approach best allows a team to expose a new feature to a small percentage of production traffic and compare outcomes against a control group?

  1. A manual review of the feature by the product owner
  2. An A/B experiment with traffic splitting and metric comparison Correct answer.
  3. A big-bang release to all users at once
  4. A code freeze until the feature is fully polished

Explanation

Traffic splitting with a control group lets the team measure the feature's effect on real users and decide based on evidence. Big-bang releases remove the comparison baseline and raise risk. Code freezes and reviews generate opinions rather than measured outcomes.

Question 41DevOps Practices (Flow, Feedback, Continual Learning)

In the Second Way, feedback should flow from right to left. Which example best illustrates that direction?

  1. Developers writing design documents for operations to implement
  2. Product managers assigning priorities to the backlog
  3. Operations staff sending production telemetry and incident findings back to developers Correct answer.
  4. Architects approving the technology stack before coding begins

Explanation

Right-to-left feedback means information generated in operations and production flows back to development so it can improve the code and process. Design documents, prioritization, and stack approval all move left to right, which is the flow direction rather than the feedback direction.

Question 42DevOps Practices (Flow, Feedback, Continual Learning)

Which practice helps a team keep its test suite fast enough to run on every commit as the codebase grows?

  1. Test parallelization with a tiered suite that runs the fastest checks first Correct answer.
  2. Removing slow tests without replacing their coverage
  3. Increasing the number of manual exploratory testers
  4. Running the full suite only before major releases

Explanation

Parallelizing tests and ordering the suite so fast checks fail early keeps commit-level feedback quick even as the suite grows. Deferring the suite to release time destroys the fast loop, and deleting coverage trades speed for escaped defects.

Question 43DevOps Practices (Flow, Feedback, Continual Learning)

A team wants to make the impact of a change visible to everyone immediately after deployment. Which combination supports this best?

  1. A weekly email summarizing last week's releases
  2. A shared folder of release notes written by hand
  3. Centralized dashboards combining deployment events with service health metrics Correct answer.
  4. A monthly meeting to review incident counts

Explanation

Correlating deployment markers with live health metrics on a shared dashboard lets anyone see within minutes whether a release changed system behavior. Weekly, monthly, or manually written summaries all introduce delay and lose the causal link between event and effect.

Question 44DevOps Practices (Flow, Feedback, Continual Learning)

Which behavior most strongly signals that an organization treats production incidents as learning opportunities rather than failures to punish?

  1. Incidents are logged without any follow-up discussion
  2. Incident reports are anonymized before being discussed
  3. Only managers are permitted to speak in incident reviews
  4. Engineers volunteer details of their own errors in reviews without fear of sanction Correct answer.

Explanation

Willingness to disclose one's own errors openly is the clearest behavioral evidence of psychological safety, which underpins learning. Anonymization, restricted discussion, and logging without review all suppress the exchange of information needed to improve.

Question 45DevOps Practices (Flow, Feedback, Continual Learning)

A team introduces automated rollback triggered by health checks. Which feedback loop does this most directly strengthen?

  1. Long-term strategic planning of the product roadmap
  2. Documentation of architectural decisions
  3. Prioritization of the backlog by business value
  4. Detection of a bad release and restoration of service with minimal delay Correct answer.

Explanation

Automated rollback closes the loop between detecting unhealthy behavior and restoring a known good state, reducing time to restore. It operates on runtime signals and does not address planning, prioritization, or documentation activities.

Question 46DevOps Practices (Flow, Feedback, Continual Learning)

An organization wants to reduce the risk that a single change causes a widespread outage. Which technique best limits the blast radius?

  1. Deploying all changes simultaneously to shorten the window
  2. Removing health checks to avoid false positives
  3. Consolidating all services into one deployable unit
  4. Progressive rollout to a small cohort before full exposure Correct answer.

Explanation

Exposing a change to a small cohort first means that if it misbehaves, only a fraction of users are affected and the rollout can be halted. Simultaneous deployment, fewer health checks, and a monolithic unit all increase the potential impact of a failure.

Question 47DevOps Practices (Flow, Feedback, Continual Learning)

Which practice most directly converts operational knowledge into faster future flow?

  1. Documenting operational procedures once at project kickoff
  2. Keeping operations in a separate department that receives finished releases
  3. Embedding operations engineers into product teams so operational constraints shape design early Correct answer.
  4. Outsourcing all production support to a third party

Explanation

When operations expertise is present during design, teams build deployable and operable systems from the start, avoiding rework and late handoffs. Separation, one-time documentation, and full outsourcing all preserve the knowledge gap that slows delivery.

Question 48DevOps Practices (Flow, Feedback, Continual Learning)

A team wants to shorten the time between discovering a defect in production and understanding its cause. Which capability matters most?

  1. A larger manual test team
  2. Correlated logs, traces, and metrics tied to a specific release Correct answer.
  3. A stricter change approval process
  4. Longer release cycles with more features per release

Explanation

Rich, correlated telemetry lets engineers trace a symptom back to the specific code path and release quickly, which is the diagnostic half of restoration. Larger test teams, longer cycles, and more approvals do not improve visibility into a running system.

Question 49DevOps Practices (Flow, Feedback, Continual Learning)

Which statement best explains why a culture of continual experimentation supports the Third Way?

  1. Teams avoid risk by freezing the release process once it works
  2. Teams centralize decision-making to reduce variation
  3. Teams learn by testing hypotheses and adjusting based on measured results Correct answer.
  4. Teams measure success only by output volume

Explanation

The Third Way emphasizes continual learning and experimentation, which requires taking deliberate risks, measuring outcomes, and adapting. Freezing processes, centralizing decisions, and counting output alone all discourage the feedback-driven adaptation that learning depends on.

Question 50DevOps Practices (Flow, Feedback, Continual Learning)

A team notices that defects found in production are rarely traced back to the change that introduced them. Which improvement addresses this most directly?

  1. Reducing the frequency of deployments to limit confusion
  2. Removing version information from build artifacts
  3. Increasing the number of manual approvals before deployment
  4. Linking each deployment to its commit history and surfacing that link in incident tooling Correct answer.

Explanation

Traceability between a running artifact, its build, and its commits lets responders identify the introducing change quickly. More approvals and fewer deployments do not create that link, and stripping version information destroys it.