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

EXIN DevOps Foundation practice questions

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

First 50 of 198 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 Basics

In DevOps, what does the term 'shift left' primarily refer to?

  1. Moving production workloads to cheaper left-side data centres
  2. Moving testing and security checks earlier into the development lifecycle Correct answer.
  3. Deploying releases only at the start of a sprint
  4. Transferring operational duties from developers to a separate ops team

Explanation

Shift left means performing quality, testing and security activities as early as possible, so defects are found when they are cheap to fix. It is a core DevOps principle because feedback loops shorten and rework decreases.

Question 2DevOps Basics

Which statement best describes the CALMS framework as used in DevOps adoption?

  1. A vendor certification path for tool administrators
  2. A five-area model covering Culture, Automation, Lean, Measurement and Sharing Correct answer.
  3. A licensing model for cloud platforms
  4. A sequential waterfall phase gate for release approval

Explanation

CALMS is a widely used mnemonic for the areas an organisation must address when adopting DevOps: Culture, Automation, Lean, Measurement and Sharing. It is a holistic model, not a process gate or a commercial scheme.

Question 3DevOps Basics

A team wants a single shared repository where developers and operations engineers raise and track incidents, changes and improvements. Which DevOps practice does this most directly support?

  1. Static code analysis
  2. Shared ownership and collaboration Correct answer.
  3. Blue-green deployment
  4. Capacity autoscaling

Explanation

DevOps culture emphasises shared responsibility between development and operations, and a common backlog or repository makes that shared ownership visible and actionable. The other options are technical practices that do not by themselves create cross-team collaboration.

Question 4DevOps Basics

What is the main purpose of a continuous integration server in a DevOps pipeline?

  1. To replace the need for version control branching
  2. To automatically build and test code changes merged into the shared mainline Correct answer.
  3. To host production databases for high availability
  4. To manage the salaries and rosters of the engineering staff

Explanation

Continuous integration servers detect changes in the shared repository, then automatically build and run automated tests so integration problems surface quickly. This provides fast feedback on every commit.

Question 5DevOps Basics

Which pair of metrics is most closely associated with the DevOps notion of flow and feedback popularised by the Accelerate research?

  1. Number of branches and commit message length
  2. Lead time for changes and mean time to restore Correct answer.
  3. Lines of code and number of meetings
  4. Headcount and office floor area

Explanation

The Accelerate/DORA research identifies four key measures: lead time for changes, deployment frequency, change failure rate and time to restore service. Lead time and restore time represent the flow and feedback dimensions respectively.

Question 6DevOps Basics

Which activity is a typical characteristic of continuous delivery rather than continuous deployment?

  1. Every change that passes the pipeline is released to production automatically
  2. Testing is performed only after the release
  3. Changes that pass the pipeline are kept releasable but a human decides when to release Correct answer.
  4. Changes are batched into a single annual release

Explanation

Continuous delivery guarantees that every validated change is deployable at any time, while the release decision can remain a deliberate business choice. Continuous deployment removes that manual gate and releases automatically.

Question 7DevOps Basics

An organisation defines 'done' for every user story as including automated tests, monitoring dashboards and runbook updates. Which DevOps principle does this definition most strongly embody?

  1. Definition of done spanning build and run concerns Correct answer.
  2. Separation of duties between build and run
  3. Fixed-scope annual budgeting
  4. Change advisory board approval

Explanation

By making operational concerns part of the definition of done, the team treats build and run as one continuous responsibility, which is central to DevOps. It prevents the classic throw-it-over-the-wall hand-off.

Question 8DevOps Basics

What distinguishes the 'three ways' of DevOps as described by Gene Kim?

  1. Plan, build, run as three sequential phases
  2. Development, testing and operations as three separate silos
  3. Systems thinking, amplified feedback loops, and a culture of continual experimentation Correct answer.
  4. Cost, quality and schedule as three competing constraints

Explanation

The three ways are flow/systems thinking, fast feedback from right to left, and continual experimentation and learning. They describe how value moves through the whole system rather than a phase model.

Question 9DevOps Basics

A team adopts infrastructure as code for its environments. Which benefit is most directly attributable to this practice?

  1. Servers no longer require any configuration
  2. Production incidents are eliminated entirely
  3. Environments become reproducible and version-controlled Correct answer.
  4. Developers no longer need to test their changes

Explanation

Infrastructure as code stores environment definitions in version control, so environments can be recreated consistently and changes reviewed like application code. It reduces drift and configuration surprises but does not remove the need for testing or configuration.

Question 10DevOps Basics

Which description best captures the role of a blameless post-mortem in DevOps?

  1. A tool that automatically rolls back the last deployment
  2. A meeting to identify which individual caused the outage
  3. A formal disciplinary procedure for repeated failures
  4. A structured review that focuses on systemic causes and learning after an incident Correct answer.

Explanation

Blameless post-mortems examine the technical and organisational conditions that allowed an incident, so people report honestly and the system improves. Blame suppresses the information needed to prevent recurrence.

Question 11DevOps Basics

A pipeline fails a build because a unit test fails. Which property of a good DevOps feedback loop does this demonstrate?

  1. Fast, automated detection close to the change Correct answer.
  2. Manual sign-off by a release manager
  3. Delayed batch verification
  4. Periodic quarterly audit

Explanation

Automated tests running at commit time give rapid, specific feedback while the change is still fresh in the developer's mind. That short feedback loop is a defining DevOps characteristic.

Question 12DevOps Basics

Which statement correctly contrasts DevOps with traditional ITIL-style change management?

  1. Traditional change management is only used for hardware
  2. DevOps eliminates all governance, whereas ITIL requires it
  3. DevOps forbids the use of any ticketing system
  4. DevOps favours small frequent low-risk changes with automated controls, while traditional change management often relies on centralised manual approval Correct answer.

Explanation

DevOps does not discard governance; it replaces heavyweight central approval of large infrequent changes with automated guardrails and small, easily reversible changes. Traditional models often treat each change as a risk requiring committee approval.

Question 13DevOps Basics

What is the primary reason DevOps teams favour small, frequent deployments over large infrequent ones?

  1. Frequent deployments remove the need for monitoring
  2. Large deployments cost more in licence fees
  3. Smaller changes are easier to review, test, and roll back, lowering risk per release Correct answer.
  4. Small changes never cause incidents

Explanation

Reducing batch size shrinks the blast radius of any single change and simplifies diagnosis and rollback. This is why deployment frequency and lower change failure rate tend to rise together.

Question 14DevOps Basics

Which practice most directly enables a team to recover quickly when a deployment turns out to be faulty in production?

  1. Requiring every change to be manually rebuilt on each server
  2. Freezing all releases for a quarter
  3. Removing monitoring to reduce alert noise
  4. Maintaining automated, repeatable deployment and rollback procedures Correct answer.

Explanation

Repeatable automated deployment makes rollback or roll-forward a routine, quick operation, which shortens time to restore service. Recovery speed is a core DevOps outcome measure.

Question 15DevOps Basics

In DevOps terminology, what is meant by 'value stream'?

  1. The sequence of activities required to take a customer request from idea to delivered value Correct answer.
  2. The financial revenue generated by the operations department
  3. The set of servers that host the production database
  4. The list of tools approved by the procurement team

Explanation

A value stream maps the end-to-end flow of work from customer need to delivered outcome, exposing waiting time and waste. Mapping it is a common first step in improving flow.

Question 16DevOps Basics

A team measures deployment frequency, lead time for changes, change failure rate and time to restore service. Which DevOps concept do these four metrics represent?

  1. The four phases of the waterfall model
  2. The four pillars of a balanced scorecard
  3. The four levels of ITIL incident severity
  4. The four DORA software delivery performance metrics Correct answer.

Explanation

These are the four key metrics identified by the DORA/Accelerate research, covering throughput and stability. They are used to benchmark software delivery performance.

Question 17DevOps Basics

Which behaviour is most consistent with a DevOps culture of psychological safety?

  1. Managers require written justification for every alert
  2. Engineers hide failed deployments to avoid punishment
  3. Engineers openly report mistakes so the team can learn and improve Correct answer.
  4. Teams avoid experimenting with new tooling

Explanation

Psychological safety means people can surface problems and errors without fear, which is a precondition for fast feedback and learning. Hiding failures blocks the improvement loop.

Question 18DevOps Basics

What is the main DevOps rationale for using version control for everything, including configuration and pipeline definitions?

  1. It provides a traceable, reviewable history so changes can be audited and reverted Correct answer.
  2. It guarantees that no bugs will ever be introduced
  3. It removes the need for automated testing
  4. It prevents developers from working in parallel

Explanation

Storing all artefacts in version control creates an auditable history, supports peer review through pull requests, and allows any change to be reverted. This traceability underpins both speed and control.

Question 19DevOps Basics

Which of the following best describes a 'fail fast' approach in DevOps engineering?

  1. Delaying test execution until after release
  2. Shutting down production whenever any alert fires
  3. Detecting and surfacing problems as early as possible so they can be corrected cheaply Correct answer.
  4. Avoiding all experimentation to prevent failure

Explanation

Fail fast means designing systems and pipelines to reveal defects early, when remediation cost is lowest. It applies to automated tests, monitoring and even feature design.

Question 20DevOps Basics

A company wants to reduce hand-offs between a development team and a separate operations team. Which structural change aligns best with DevOps principles?

  1. Increase the number of formal sign-off stages
  2. Create a cross-functional product team that builds and runs its own service Correct answer.
  3. Outsource operations to a distant time zone
  4. Add a third team to coordinate between the two existing teams

Explanation

DevOps recommends cross-functional teams with end-to-end responsibility, often called 'you build it, you run it'. This removes hand-off delays and aligns incentives with service reliability.

Question 21DevOps Basics

Which statement about the relationship between DevOps and Agile is most accurate?

  1. Agile applies only to operations and DevOps only to development
  2. Agile focuses on iterative delivery of working software, while DevOps extends the same thinking into deployment and operations Correct answer.
  3. The two approaches are unrelated and cannot be combined
  4. DevOps replaces Agile entirely and forbids iterations

Explanation

Agile addresses how teams plan and build in short iterations, while DevOps extends agility through release and operations so that delivered software actually reaches users reliably. They are complementary.

Question 22DevOps Basics

An engineer proposes tracking the number of story points delivered per sprint as the main DevOps success measure. What is the strongest criticism of this choice?

  1. It violates the CALMS principle of automation
  2. It is impossible to count story points in any tool
  3. It measures local output rather than end-to-end delivery outcomes such as lead time and stability Correct answer.
  4. It is the only metric approved by the DORA research

Explanation

Story point velocity measures a team's local planning throughput and can be gamed; it says nothing about how quickly value reaches customers or how stable the service is. DevOps favours outcome metrics spanning the whole value stream.

Question 23DevOps Basics

Which scenario best illustrates the DevOps concept of 'you build it, you run it'?

  1. A development team carries the pager for its own service and fixes production issues it causes Correct answer.
  2. A vendor is contractually responsible for all incidents
  3. A developer writes code and hands it to a separate team that owns all production support
  4. An external auditor approves each deployment manually

Explanation

When the team that builds a service also operates it, feedback about production behaviour flows directly back into design and code. This tightens accountability and shortens learning cycles.

Question 24DevOps Basics

Which combination of practices most directly supports continuous delivery of a microservice?

  1. Manual release notes, quarterly change windows, and shared admin accounts
  2. Long-lived feature branches merged once a year
  3. Automated testing, infrastructure as code, and a deployment pipeline Correct answer.
  4. Separate source repositories per environment and manual server configuration

Explanation

Continuous delivery relies on automated verification, reproducible environments and an automated pipeline that can promote any validated build. These together keep the service releasable at all times.

Question 25DevOps Basics

What is the purpose of a deployment pipeline in DevOps?

  1. To document the organisational chart
  2. To replace the need for a product owner
  3. To store backups of the production database
  4. To automate the stages that move a change from commit through testing to release Correct answer.

Explanation

A deployment pipeline encodes the build, test and release steps as an automated sequence, giving consistent, visible and repeatable promotion of changes. It is the technical backbone of continuous delivery.

Question 26DevOps Basics

Which statement best defines DevOps as the term is used in this exam?

  1. A programming language designed for writing infrastructure configuration files
  2. A formal certification scheme that replaces existing IT service management frameworks
  3. A cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals Correct answer.
  4. A software tool that automatically installs, configures and monitors servers across multiple cloud providers

Explanation

DevOps is generally defined as a cultural and professional movement, not a product or a standard. It emphasises collaboration and integration between development and operations across the whole delivery lifecycle. Tools support the movement but do not define it.

Question 27DevOps Basics

Which pair of organisational outcomes is most closely associated with adopting DevOps?

  1. Separation of build and run duties and reduced developer access to production
  2. Faster delivery of changes and more stable services in production Correct answer.
  3. Larger release batches and fewer automated tests
  4. Stricter change approval boards and longer release cycles

Explanation

DevOps aims to improve both speed and stability at the same time, rather than trading one for the other. Faster flow of changes and fewer failures in production are the twin goals described in DevOps literature. The other options describe traditional trade-offs that DevOps seeks to overcome.

Question 28DevOps Basics

In DevOps thinking, what does the term 'flow' refer to?

  1. The rate at which new employees are onboarded into a team
  2. The network traffic between microservices measured during load testing
  3. The sequence of approval signatures required before a release
  4. The movement of work from development through to production without unnecessary waiting or rework Correct answer.

Explanation

Flow describes how work moves through the value stream towards the customer, with the aim of removing bottlenecks and delays. It is the focus of the first way in Gene Kim's framing. Network traffic, approvals and onboarding are unrelated uses of the word.

Question 29DevOps Basics

Which practice gives a DevOps team the ability to rebuild an identical environment on demand?

  1. Relying on a single senior engineer who remembers the configuration
  2. Manually documenting server settings in a shared spreadsheet
  3. Restoring a virtual machine snapshot taken once a year
  4. Treating infrastructure definitions as versioned code that is applied automatically Correct answer.

Explanation

Infrastructure as code stores environment definitions in version control and applies them through automation, so environments can be recreated reliably. Manual documentation and individual memory are not reproducible. Annual snapshots do not provide on-demand rebuilds.

Question 30DevOps Basics

Which term describes a small, cross-functional team that owns a service from idea through operation?

  1. Outsourced operations vendor
  2. Product team with end-to-end ownership Correct answer.
  3. Centre of excellence with advisory-only duties
  4. Separate build team and run team with a handover

Explanation

DevOps favours teams that own a service across its whole lifecycle, including running it in production. This end-to-end ownership shortens feedback loops and accountability gaps. Advisory centres, split teams and outsourcing reintroduce handovers.

Question 31DevOps Basics

What is the main purpose of a blameless culture in DevOps incident handling?

  1. To remove the need for incident reviews after a service outage
  2. To ensure that no one is ever held accountable for ignoring documented procedures
  3. To encourage people to report problems and near misses so that systemic causes can be fixed Correct answer.
  4. To prevent managers from learning the names of engineers involved in failures

Explanation

Blameless culture removes fear of punishment so that accurate information about failures surfaces. The aim is to correct systemic causes rather than single out individuals. It does not abolish accountability or incident review.

Question 32DevOps Basics

Which statement describes the DevOps view of automation?

  1. Automation is only worthwhile for large enterprises with dedicated tooling teams
  2. Automation should be applied to repetitive, error-prone tasks so that people can focus on higher-value work Correct answer.
  3. Automation should replace all human decision-making in production
  4. Automation should be avoided because scripts inevitably drift from documentation

Explanation

DevOps treats automation as a way to remove toil and reduce human error in repetitive work. People remain responsible for judgement and design. Automation is valuable to teams of any size and script drift is managed through version control.

Question 33DevOps Basics

Which concept describes measuring how long a change takes from commit to running in production?

  1. Lead time for changes Correct answer.
  2. Story point velocity
  3. Server uptime percentage
  4. Mean time between failures

Explanation

Lead time for changes measures the elapsed time from code committed to code running in production. It is one of the four key DevOps metrics alongside deployment frequency, change failure rate and time to restore. Velocity, uptime and failure intervals measure different things.

Question 34DevOps Basics

A retailer wants developers to receive feedback on integration problems within minutes of pushing code. Which DevOps practice addresses this most directly?

  1. Scheduling a monthly integration test weekend
  2. Deploying all changes to production only at quarter end
  3. Requiring manual code review before any branch can be merged
  4. Running an automated continuous integration build and test suite on every commit Correct answer.

Explanation

Continuous integration automatically builds and tests each commit, giving rapid feedback on integration problems. Monthly testing, manual gates and quarterly releases all lengthen the feedback loop. The goal is fast detection close to the moment of change.

Question 35DevOps Basics

A team's deployment pipeline runs unit tests, then integration tests, then a security scan, stopping at the first failure. What is the primary benefit of this ordering?

  1. It guarantees that no security vulnerability can ever reach production
  2. It removes the need for any manual approval before release
  3. It makes the pipeline independent of version control
  4. Cheap, fast checks fail early so that slower stages are not wasted on broken builds Correct answer.

Explanation

Ordering stages from fastest and cheapest to slowest and most expensive means broken builds are rejected before costly stages run. This conserves resources and shortens feedback time. No pipeline ordering can guarantee zero vulnerabilities or eliminate version control.

Question 36DevOps Basics

An operations engineer is embedded in a product team and helps design logging and alerting before the first release. Which DevOps principle does this best illustrate?

  1. Increasing the number of approval gates before release
  2. Delegating all operational knowledge to a central ticket queue
  3. Separating test environments from production permanently
  4. Shifting operational concerns left into earlier design stages Correct answer.

Explanation

Bringing operational expertise into design is an example of shifting left, so that operability is built in rather than bolted on. It reduces late surprises and rework. Ticket queues, extra gates and permanent environment separation work against this principle.

Question 37DevOps Basics

A team wants to limit the blast radius of a faulty release while still shipping frequently. Which combination best achieves this?

  1. Feature flags and canary releases Correct answer.
  2. Longer code freeze periods and larger release batches
  3. Removing monitoring to reduce alert noise
  4. A single annual release window and manual rollback scripts

Explanation

Feature flags decouple deployment from release, and canary releases expose only a small portion of traffic to a new version. Together they contain the impact of defects while preserving delivery speed. Freezes, big batches and reduced monitoring increase risk.

Question 38DevOps Basics

Why do DevOps teams prefer to keep configuration in the same version control repository as application code?

  1. It removes the need to test configuration changes
  2. Configuration changes become traceable, reviewable and revertible alongside the code they affect Correct answer.
  3. It allows developers to bypass code review for configuration
  4. It guarantees that configuration can never contain secrets

Explanation

Storing configuration with code gives a single history, so changes can be reviewed, traced and reverted together. It does not make secrets safe to commit and does not remove the need for testing. Bypassing review would undermine the benefit.

Question 39DevOps Basics

A manager proposes measuring DevOps success solely by the number of automated tests in the suite. What is the main weakness of this measure?

  1. Test counts are impossible to collect from a pipeline
  2. Test count says nothing about whether tests are meaningful or whether delivery outcomes improve Correct answer.
  3. Only manual testing provides useful feedback in DevOps
  4. Automated tests are irrelevant to DevOps and should not be counted at all

Explanation

Counting tests measures activity rather than outcome and can be gamed by adding trivial tests. DevOps success is better judged by delivery and reliability outcomes such as lead time and change failure rate. Tests remain valuable, but volume alone is a poor indicator.

Question 40DevOps Basics

What does 'continuous delivery' require of a codebase so that any commit can be released on demand?

  1. The code is always in a deployable state and passes automated verification Correct answer.
  2. Every commit is automatically released to all customers immediately
  3. Releases are batched into a single annual event
  4. Developers deploy manually from their local machines

Explanation

Continuous delivery keeps the mainline releasable at all times, verified by automated tests. The business decides when to release, which distinguishes it from continuous deployment. Annual batching and local manual deploys contradict the practice.

Question 41DevOps Basics

A team holds a short daily session where members discuss impediments to the flow of work rather than reporting to a manager. Which DevOps value does this reflect most directly?

  1. Individual performance ranking
  2. Collaboration and transparency across the delivery team Correct answer.
  3. Strict command-and-control management
  4. Segregation of duties between development and operations

Explanation

Short, transparent team sessions surface blockers early and support shared ownership of flow. They are collaborative rather than managerial reporting rituals. Ranking individuals or separating duties would undermine the purpose.

Question 42DevOps Basics

Which practice most directly reduces the time needed to diagnose a production incident?

  1. Longer change approval meetings
  2. Centralised logging and distributed tracing correlated by request identifier Correct answer.
  3. Removing alerting thresholds to reduce noise
  4. Fewer deployment events per quarter

Explanation

Centralised logs and tracing let engineers follow a request across services and pinpoint the failure quickly. Faster diagnosis shortens restoration time. Approval meetings, fewer deployments and removed alerts do not improve observability.

Question 43DevOps Basics

A team defines its service level objective for checkout availability at 99.9 per cent per month. How should this objective influence release decisions?

  1. It removes the need for monitoring because the target is contractual
  2. It means the service must never be changed during the month
  3. It sets an error budget that constrains how much risk releases may take within the period Correct answer.
  4. It requires every release to be approved by the finance department

Explanation

An error budget derived from the objective quantifies acceptable unreliability and guides release risk decisions. Teams can move faster while budget remains and slow down when it is exhausted. It neither blocks all change nor replaces monitoring.

Question 44DevOps Basics

Which situation best demonstrates that a team has achieved a genuine DevOps culture rather than only adopting tools?

  1. Automation is widespread but blame is assigned to whoever last touched the failing code
  2. The team owns the newest pipeline tool but still hands releases to a separate operations group
  3. Operations writes runbooks that developers are not permitted to read
  4. Developers and operations staff jointly own incident response and share on-call duties Correct answer.

Explanation

Culture is shown by shared ownership and joint accountability, not by tooling alone. Shared on-call and joint incident response align incentives across the lifecycle. Tool adoption with handovers, blame or information barriers leaves the old culture intact.

Question 45DevOps Basics

Why does DevOps recommend making work visible on a shared board or dashboard?

  1. It exposes bottlenecks and queues so the team can limit work in progress and improve flow Correct answer.
  2. It guarantees that no work item is ever delayed
  3. It allows managers to rank individual engineers by output
  4. It replaces the need for automated testing

Explanation

Visualising work reveals queues, bottlenecks and overload, which supports limiting work in progress and improving flow. It is a flow-management aid, not a ranking tool. It cannot replace testing or guarantee the absence of delays.

Question 46DevOps Basics

A team replaces its manual release checklist with an automated pipeline that performs the same steps. Which outcome should it expect?

  1. Elimination of the need to review the release process ever again
  2. Slower releases because automation is always less efficient than people
  3. More consistent releases and fewer human errors, with the checklist knowledge preserved as code Correct answer.
  4. Loss of all control over what happens during a release

Explanation

Encoding a checklist as pipeline code makes execution repeatable and removes slips caused by manual steps. The process still needs periodic review as conditions change. Automation is generally faster and more consistent than manual execution.

Question 47DevOps Basics

An organisation claims to practise continuous delivery, yet releases still require a two-week manual regression cycle. Which conclusion is most defensible?

  1. Continuous delivery only applies to teams that release daily
  2. The manual regression cycle contradicts continuous delivery because releasability is not verified automatically and on demand Correct answer.
  3. The manual cycle is acceptable provided deployments are frequent
  4. The organisation is practising continuous deployment because it releases regularly

Explanation

Continuous delivery requires that any commit can be released on demand, which depends on automated verification. A two-week manual regression gate means releasability is neither fast nor repeatable. Frequent releases and daily cadence are not the defining criterion.

Question 48DevOps Basics

A team's change failure rate rises while its deployment frequency also rises. What is the most useful DevOps interpretation?

  1. The team should stop deploying frequently until the failure rate is zero
  2. The failure rate proves that DevOps practices cause instability
  3. The team should remove automated tests to speed the pipeline further
  4. The team should examine whether smaller batches and stronger automated checks can restore the balance between speed and stability Correct answer.

Explanation

Speed and stability are meant to improve together, so a rising failure rate signals that verification or batch size needs attention. The response is to strengthen feedback and reduce risk per change, not to abandon frequent delivery. A zero failure rate is not a realistic target.

Question 49DevOps Basics

Why is a loosely coupled architecture considered an enabler of DevOps performance?

  1. It forces all teams to release on the same schedule
  2. It removes the need for any integration testing between services
  3. Teams can deploy their components independently, reducing coordination cost and blast radius Correct answer.
  4. It guarantees that services will never fail in production

Explanation

Loose coupling lets teams change and deploy their own services without coordinating every release across the whole system. That lowers coordination cost and limits the impact of failures. It does not eliminate integration testing or prevent failures.

Question 50DevOps Basics

A regulated organisation must retain a documented approval for production changes while still adopting DevOps. Which approach best reconciles these requirements?

  1. Automate evidence collection and approvals within the pipeline so compliance is continuously demonstrated Correct answer.
  2. Abandon the regulatory requirement because DevOps supersedes it
  3. Deploy without records and reconstruct the audit trail after an inspection
  4. Retain manual approval boards for every small change and accept slow delivery

Explanation

Compliance can be satisfied through automated evidence gathering and policy checks embedded in the pipeline, preserving both speed and auditability. Manual boards for every change reintroduce delay, while ignoring or reconstructing records creates regulatory risk.