

















































































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
This certification exam guide is designed for senior leaders overseeing DevOps transformation. It covers DevOps strategy, governance, organizational change, performance metrics, and business alignment. Candidates gain insight into driving DevOps initiatives at an enterprise level.
Typology: Exams
1 / 89
This page cannot be seen from the preview
Don't miss anything!


















































































Question 1. Which of the following best describes a Generative organizational culture according to Westrum’s model? A) High fear of failure and strict hierarchy B) Formalized procedures with limited autonomy C) Encourages learning, sharing of information, and rapid experimentation D) Relies on command‑and‑control decision making Answer: C Explanation: A Generative culture promotes openness, collaboration, and continuous learning, enabling fast feedback and innovation. Question 2. In the Three Ways of DevOps, “Flow” primarily focuses on: A) Automating security testing B) Reducing hand‑offs and batch sizes to accelerate delivery C) Conducting post‑mortems after incidents D) Establishing governance committees Answer: B Explanation: Flow is about creating smooth, fast movement of work from development to operations by minimizing delays and batch sizes. Question 3. Which leadership style most effectively fosters “Intellectual Stimulation” in a DevOps transformation? A) Autocratic B) Transformational C) Transactional D) Laissez‑faire Answer: B
Explanation: Transformational leaders challenge assumptions and encourage innovative thinking, which aligns with intellectual stimulation. Question 4. When mapping a Value Stream, “Touch Time” refers to: A) The total calendar time a work item spends in the system B) The time a person or system actively works on the item C) The waiting time between process steps D) The time required for documentation Answer: B Explanation: Touch Time is the actual effort time, whereas Wait Time is the idle period. Question 5. In Theory of Constraints, the “Elevating the Constraint” step means: A) Adding more resources to the bottleneck without process change B) Redesigning the workflow to remove the bottleneck’s impact C) Ignoring the bottleneck and focusing on other areas D) Outsourcing the constrained activity Answer: B Explanation: Elevating the constraint involves improving or redesigning the bottleneck to increase overall throughput. Question 6. Which funding model aligns best with a product‑centric DevOps organization? A) Capital‑expenditure (CapEx) project budgeting B) Operational‑expenditure (OpEx) product funding C) Time‑and‑materials contracts D) Fixed‑price contracts per release Answer: B
D. Uniform on‑premise hardware for all teams Answer: B Explanation: Self‑service portals give teams the ability to provision resources without gatekeepers, enhancing autonomy. Question 10. The “Definition of Done” in a CI/CD pipeline should include: A. Only successful compilation of code B. Deployment to production without any testing C. Automated unit, integration, and security tests passing, plus documentation updated D. Manual approval from a manager before release Answer: C Explanation: A robust Definition of Done ensures quality, security, and documentation are completed before code is considered releasable. Question 11. Technical debt is best visualized using which of the following artifacts? A. Gantt chart B. Debt radar chart showing dimensions such as maintainability, reliability, and performance C. Burn‑down chart of story points D. Organizational hierarchy diagram Answer: B Explanation: A debt radar provides a multi‑dimensional view of debt, helping prioritize remediation. Question 12. “Shifting Left” in DevSecOps primarily means: A. Performing security testing after production release B. Integrating security checks early in the development lifecycle
C. Deferring compliance documentation until the end of the quarter D. Outsourcing security to a third‑party vendor Answer: B Explanation: Shifting Left moves security activities to earlier stages, catching defects sooner. Question 13. Which of the following is an example of an automated “Guardrail” in a deployment pipeline? A. Manual code review checklist B. Automated policy enforcement that blocks deployments with known vulnerabilities C. Post‑deployment manual health check D. Email notification to the security team after release Answer: B Explanation: Guardrails are automated controls that enforce policies without human intervention. Question 14. In resilience engineering, why is MTTR (Mean Time to Recover) considered more important than MTBF (Mean Time Between Failures)? A. MTTR measures how quickly a system can be restored, directly impacting availability B. MTBF is irrelevant for cloud‑native systems C. MTTR is easier to calculate than MTBF D. MTBF only applies to hardware components Answer: A Explanation: In high‑velocity environments, rapid recovery reduces user impact, making MTTR a key metric. Question 15. Which practice helps satisfy auditors in a continuous delivery environment?
Question 18. An OKR for a DevOps team that aligns with corporate revenue goals might be: A. “Increase the number of daily builds to 10” B. “Reduce mean time to restore service to under 30 minutes” C. “Implement a new CI tool by Q3” D. “Maintain 100% test coverage” Answer: B Explanation: Reducing MTTR directly improves service availability, supporting revenue and customer experience. Question 19. In the Lean Startup Cycle, the “Measure” phase primarily involves: A. Writing user stories B. Deploying a prototype to production without metrics C. Collecting validated learning through analytics and experiments D. Conducting a feasibility study Answer: C Explanation: The Measure step gathers data to test hypotheses and inform decisions. Question 20. Observability differs from traditional monitoring by emphasizing: A. Only threshold‑based alerts B. The ability to ask arbitrary questions about system state using telemetry data C. Manual log review by engineers D. Static dashboards with fixed metrics Answer: B Explanation: Observability provides rich, contextual data (metrics, logs, traces) enabling dynamic queries.
Question 21. Which of the following is a common sign of a “Pathological” culture in a software organization? A. Open sharing of failures to learn B. High blame culture with fear of reporting problems C. Empowered teams making autonomous decisions D. Continuous improvement initiatives Answer: B Explanation: Pathological cultures are characterized by fear, blame, and resistance to change. Question 22. A key benefit of “Continuous Feedback” in the Three Ways is: A. Eliminating the need for retrospectives B. Reducing the number of automated tests C. Early detection of defects and alignment with business goals D. Slowing down releases to ensure stability Answer: C Explanation: Continuous feedback provides rapid insight into quality and business value, enabling quick adjustments. Question 23. In Value Stream Mapping, a “non‑value‑added” activity is one that: A. Directly contributes to the customer’s requirements B. Is required by compliance but does not add functional value C. Reduces lead time for changes D. Improves system reliability Answer: B
D. Monolithic deployment capabilities Answer: C Explanation: A service mesh abstracts communication, security, and telemetry for microservices. Question 27. Which of the following best exemplifies “Infrastructure as Code” (IaC)? A. Manually configuring servers via SSH B. Using a version‑controlled script to provision cloud resources automatically C. Documenting network diagrams on a wiki D. Relying on a third‑party vendor to manage hardware Answer: B Explanation: IaC treats infrastructure definitions as code, enabling automated, repeatable provisioning. Question 28. When moving from CapEx to OpEx funding, which financial metric becomes more relevant for decision‑making? A. Return on Investment (ROI) per project B. Annualized Cost of Ownership (ACoO) C. Total Capital Expenditure (TCE) D. Fixed asset depreciation schedule Answer: B Explanation: OpEx focuses on ongoing operational costs, making ACoO a key metric. Question 29. Which practice directly supports “Continuous Learning” in the Three Ways? A. Conducting post‑incident blameless postmortems B. Enforcing strict release windows
C. Limiting access to production logs D. Requiring all changes to be approved by senior management Answer: A Explanation: Blameless postmortems turn failures into learning opportunities, fostering a culture of continuous improvement. Question 30. A “Feature Toggle” is used to: A. Permanently remove code from the codebase B. Dynamically enable or disable functionality without redeploying C. Encrypt data in transit D. Scale databases automatically Answer: B Explanation: Feature toggles allow selective activation of features at runtime, supporting safe releases. Question 31. Which of the following is a leading indicator that a team is moving toward a Generative culture? A. Increased number of escalations to senior management B. Higher frequency of knowledge‑sharing sessions and cross‑team collaborations C. Strict adherence to siloed responsibilities D. Longer approval cycles for changes Answer: B Explanation: Generative cultures emphasize collaboration and learning, reflected in frequent knowledge sharing. Question 32. In the context of DevSecOps, “Static Application Security Testing” (SAST) is performed at which stage?
Question 35. Which of the following statements about “Mean Time Between Failures” (MTBF) is true? A. It measures the average time to recover from a failure B. It is more relevant for systems where failure prevention is the primary goal C. It is calculated after each incident D. It is the same as MTTR Answer: B Explanation: MTBF focuses on reliability and the interval between failures, useful when preventing failures is critical. Question 36. A “Brownfield” migration refers to: A. Building a new system from scratch in the cloud B. Incrementally modernizing an existing on‑premise application while it remains operational C. Moving only data, not code, to a new platform D. Decommissioning legacy systems without replacement Answer: B Explanation: Brownfield migration modernizes existing applications without full rewrite. Question 37. Which practice helps reduce “Change Failure Rate” in a CI/CD pipeline? A. Increasing batch size of changes per release B. Adding extensive manual testing after deployment C. Implementing automated canary analysis and rollback mechanisms D. Delaying security scans until after production release Answer: C
Explanation: Automated canary analysis detects issues early, and automated rollbacks limit impact, reducing failure rates. Question 38. In an OKR framework, the “Key Result” should be: A. A vague aspiration B. A qualitative statement without metrics C. A measurable outcome that indicates progress toward the Objective D. A task list for individual developers Answer: C Explanation: Key Results are quantifiable metrics that track achievement of the Objective. Question 39. Which of the following is a primary advantage of “GitOps” for deployment automation? A. Manual approval steps for every change B. Storing the desired state of the system in a Git repository, enabling declarative deployments C. Requiring developers to write custom scripts for each environment D. Eliminating the need for version control Answer: B Explanation: GitOps treats Git as the source of truth for infrastructure and applications, enabling automated, repeatable deployments. Question 40. A “Service Level Objective” (SLO) is typically expressed as: A. A qualitative description of service quality B. A target metric (e.g., 99.9 % availability) agreed upon with users C. The total cost of ownership of a service D. The number of developers assigned to the service
C. Manual provisioning of additional servers by ops staff D. Using a single large monolithic server Answer: B Explanation: Serverless platforms automatically adjust compute resources in response to workload spikes. Question 44. The practice of “Trunk‑Based Development” primarily aims to: A. Encourage long‑lived feature branches B. Reduce merge conflicts and enable continuous integration C. Separate development and production codebases entirely D. Increase the number of release branches Answer: B Explanation: Trunk‑based development keeps code on a single branch, facilitating frequent integration and reducing integration pain. Question 45. Which of the following is a core principle of the “Lean Startup” methodology? A. Build large, fully featured products before market testing B. Validate hypotheses through rapid experiments and iterate based on feedback C. Avoid any form of customer interaction until product launch D. Prioritize internal stakeholder satisfaction over external users Answer: B Explanation: Lean Startup emphasizes quick cycles of building, measuring, and learning to validate business ideas. Question 46. A “Chaos Engineering” experiment typically involves: A. Randomly deleting production data to test backups
B. Introducing controlled failures to verify system resiliency C. Rewriting code in production without testing D. Scaling down all services to zero capacity Answer: B Explanation: Chaos Engineering deliberately injects failures to ensure the system can recover gracefully. Question 47. Which metric is most directly impacted by the use of “Feature Flags”? A. Deployment Frequency B. Mean Time to Recover (MTTR) C. Change Failure Rate (by enabling safe roll‑backs) D. Lead Time for Changes Answer: C Explanation: Feature flags allow quick disabling of problematic features, reducing the chance of a change causing failure. Question 48. What is the primary purpose of a “Runbook” in an operations context? A. To document source code architecture B. To provide step‑by‑step procedures for handling incidents and routine tasks C. To outline the company’s strategic roadmap D. To list all team members and their roles Answer: B Explanation: Runbooks standardize responses to incidents, aiding rapid recovery. Question 49. In the context of DevSecOps, “Dynamic Application Security Testing” (DAST) is performed:
Explanation: Smaller, more frequent deployments lower batch size, improving flow and feedback. Question 52. Which of the following is a typical outcome of implementing “Value Stream Mapping” in a software organization? A. Increased number of manual hand‑offs B. Identification and elimination of wasteful steps C. Longer lead times for changes D. Higher change failure rates Answer: B Explanation: VSM highlights inefficiencies, enabling teams to remove non‑value‑added activities. Question 53. In a DevOps context, “Shift‑Right” testing primarily focuses on: A. Performing security scans earlier in the pipeline B. Conducting extensive testing in production to gather real‑user data C. Automating unit tests before code commit D. Removing all testing from the delivery process Answer: B Explanation: Shift‑Right emphasizes testing in the live environment to validate behavior under real conditions. Question 54. Which of the following best illustrates “Automation as Code” in governance? A. Writing policy documents in Word and storing them on a shared drive B. Defining compliance rules in a version‑controlled DSL that can be applied automatically to pipelines C. Conducting manual audits quarterly
D. Using spreadsheets to track change approvals Answer: B Explanation: Automation as Code codifies governance policies, enabling consistent, automated enforcement. Question 55. The “Mean Time to Detect” (MTTD) metric is most useful for: A. Measuring how quickly a team can develop new features B. Assessing the speed of incident detection, which influences overall MTTR C. Calculating the average time between releases D. Determining the cost of infrastructure Answer: B Explanation: Faster detection shortens the overall incident resolution time. Question 56. Which of the following is a key characteristic of a “Product‑Centric” organization? A. Funding is allocated per project with a fixed end date B. Teams own the product end‑to‑end, including operations and support C. Development and operations are separate, siloed departments D. Releases are scheduled only annually Answer: B Explanation: Product‑centric organizations give teams responsibility for the entire product lifecycle. Question 57. In a microservices architecture, “Circuit Breaker” patterns are used to: A. Increase the number of microservices automatically B. Prevent cascading failures by stopping calls to unhealthy services