












































































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
The DevOps Foundation Exam provides a comprehensive introduction to DevOps concepts, culture, and practices. It covers Agile alignment, continuous integration, continuous delivery, automation, monitoring, and collaboration models. The exam establishes a strong baseline for DevOps career pathways.
Typology: Exams
1 / 84
This page cannot be seen from the preview
Don't miss anything!













































































Question 1. Which of the following most accurately describes DevOps as a cultural shift rather than a toolset? A) Installing a new CI server automatically improves collaboration. B) Replacing all legacy systems with cloud services. C) Encouraging shared responsibility and communication between development and operations. D) Mandating the use of Docker for all applications. Answer: C Explanation: DevOps emphasizes cultural change—shared ownership, collaboration, and communication—over any single technology. Question 2. The progression from Waterfall to Agile to DevOps primarily reflects a move toward: A) Longer release cycles. B) Increased documentation. C) Faster feedback and continuous delivery. D) More rigid hierarchical structures. Answer: C Explanation: Each step in the evolution focuses on shortening feedback loops and delivering value more rapidly. Question 3. Which value proposition is NOT directly associated with adopting DevOps practices? A) Higher deployment frequency. B) Longer lead time for changes. C) Lower change failure rate. D) Faster mean time to recovery (MTTR). Answer: B
Explanation: DevOps aims to reduce lead time, not increase it. Question 4. The First Way of the Three Ways in DevOps focuses on: A) Creating rapid feedback loops. B) Optimizing the flow of work from development to operations. C) Encouraging a culture of experimentation. D) Automating security testing. Answer: B Explanation: The First Way emphasizes smooth, fast flow of work across the value stream. Question 5. In the Three Ways, the Second Way is primarily about: A) Continuous integration. B) Feedback loops from operations back to development. C) Automating infrastructure provisioning. D) Scaling microservices. Answer: B Explanation: The Second Way stresses fast and constant feedback from right to left (operations to development). Question 6. The Third Way of DevOps encourages: A) Strict adherence to process without change. B) High‑trust culture and scientific experimentation. C) Manual hand‑offs between teams. D) Isolating development from production. Answer: B Explanation: The Third Way promotes learning, experimentation, and a high‑trust environment.
Question 10. A “Two‑Pizza” team is defined as: A) A team that can be fed with two pizzas, typically 6–10 people. B) A team that works on two projects simultaneously. C) A group that follows a strict hierarchy. D) A team that only uses two programming languages. Answer: A Explanation: The term emphasizes small, cross‑functional teams small enough to be fed by two pizzas. Question 11. Psychological safety in a DevOps team is best demonstrated by: A) Assigning blame after every failure. B) Conducting blameless post‑mortems. C) Restricting access to production. D) Enforcing strict code reviews. Answer: B Explanation: Blameless post‑mortems encourage learning without fear of punishment. Question 12. The shift from “I do my job” to “I am responsible for the product” reflects a change in: A. Tool selection. B. Organizational hierarchy. C. Ownership and accountability. D. Programming language choice. Answer: C Explanation: This shift emphasizes collective product responsibility across teams. Question 13. Which strategy is most effective for managing resistance to DevOps adoption?
A. Mandating tools without training. B. Ignoring dissenting voices. C. Involving stakeholders early and demonstrating quick wins. D. Replacing all legacy staff. Answer: C Explanation: Early involvement and visible benefits help reduce resistance. Question 14. DevSecOps primarily aims to: A. Add security after deployment. B. Shift security testing to the left, integrating it early. C. Replace developers with security engineers. D. Eliminate all automated testing. Answer: B Explanation: DevSecOps embeds security practices early in the development lifecycle. Question 15. Which version control system is distributed rather than centralized? A. Subversion (SVN). B. Perforce. C. Git. D. CVS. Answer: C Explanation: Git is a distributed version control system. Question 16. In the testing pyramid, which type of test should have the highest number of automated tests? A. End‑to‑end tests.
C. Increase the number of microservices. D. Replace all databases. Answer: B Explanation: Blue‑green swaps traffic between two identical environments, ensuring quick rollback. Question 20. Canary releases are useful for: A. Deploying to 100% of users instantly. B. Testing new features on a small subset of users before full rollout. C. Eliminating the need for monitoring. D. Automatically generating documentation. Answer: B Explanation: Canary releases expose changes to a limited audience to detect issues early. Question 21. Feature flags enable teams to: A. Hard‑code configuration values. B. Toggle functionality at runtime without redeploying. C. Remove all automated tests. D. Disable version control. Answer: B Explanation: Feature flags allow dynamic activation/deactivation of features. Question 22. Infrastructure as Code (IaC) is best described as: A. Manual server provisioning. B. Storing configuration in spreadsheets. C. Defining infrastructure through machine‑readable files.
D. Outsourcing all infrastructure to a third party. Answer: C Explanation: IaC uses code (e.g., Terraform, CloudFormation) to provision and manage infrastructure. Question 23. Which tool is primarily used for source code management? A. Jenkins. B. Ansible. C. GitHub. D. Prometheus. Answer: C Explanation: GitHub hosts Git repositories for source code management. Question 24. In a CI/CD pipeline, which stage typically follows automated unit testing? A. Production deployment. B. Integration testing. C. Requirements gathering. D. Manual code review. Answer: B Explanation: After unit tests, pipelines usually run integration tests before further stages. Question 25. Which configuration management tool uses a declarative language called “Puppet DSL”? A. Chef. B. Ansible. C. Puppet. D. Terraform.
Explanation: Serverless platforms handle server management, allowing developers to focus on code. Question 29. Which of the following best illustrates the difference between virtualization and containerization? A. Virtual machines run separate OS kernels; containers share the host kernel. B. Containers require more hardware resources than VMs. C. Virtualization cannot run on cloud platforms. D. Containers cannot be orchestrated. Answer: A Explanation: VMs emulate hardware and run full OS instances; containers share the host OS. Question 30. The DORA metric “Deployment Frequency” measures: A. Number of bugs per release. B. How often code is successfully released to production. C. Average code review time. D. Number of developers on a team. Answer: B Explanation: Deployment Frequency tracks how many production releases occur in a given period. Question 31. Lead Time for Changes is defined as the time between: A. Code commit and code push to the repository. B. Code commit and code running in production. C. Issue creation and issue closure. D. Sprint planning and sprint review. Answer: B
Explanation: Lead Time for Changes measures the duration from commit to live production. Question 32. Change Failure Rate quantifies: A. Percentage of deployments causing a production incident. B. Number of lines of code changed per sprint. C. Frequency of code merges. D. Time spent on documentation. Answer: A Explanation: It reflects the proportion of releases that result in failures. Question 33. Mean Time to Restore Service (MTTR) captures: A. Average time to develop a new feature. B. Time taken to recover from a production incident. C. Duration of daily stand‑up meetings. D. Length of a sprint. Answer: B Explanation: MTTR measures how quickly a service is restored after a failure. Question 34. The Four Golden Signals of monitoring include all EXCEPT: A. Latency. B. Traffic. C. Errors. D. Code coverage. Answer: D Explanation: Code coverage is a testing metric, not a golden signal.
B. Knowledge transfer through communities of practice. C. Isolating teams from each other. D. Reducing automation. Answer: B Explanation: Sharing promotes collaboration and learning across the organization. Question 39. Which of the following is a typical characteristic of a “blameless post‑mortem”? A. Assigning individual fault scores. B. Focusing on systemic improvements rather than personal blame. C. Ignoring the incident entirely. D. Disabling monitoring after an outage. Answer: B Explanation: Blameless post‑mortems aim to learn without attributing blame. Question 40. Which practice best supports the “Shift Left” security approach? A. Conducting penetration testing only after production. B. Integrating static code analysis into CI pipelines. C. Deferring security reviews until the release phase. D. Disabling all security checks to speed up builds. Answer: B Explanation: Embedding security checks early in CI embodies “Shift Left”. Question 41. A monorepo strategy is most beneficial when: A. Teams need completely isolated codebases. B. Multiple projects share common libraries and need coordinated changes.
C. Projects are written in different programming languages. D. You want to avoid any merge conflicts. Answer: B Explanation: A monorepo facilitates shared code and coordinated updates across projects. Question 42. Which Git workflow encourages short-lived feature branches and frequent merges to the main branch? A. Git Flow. B. Trunk‑Based Development. C. Fork‑and‑Pull. D. Release Branching. Answer: B Explanation: Trunk‑Based Development uses short branches or direct commits to the main line. Question 43. In a CI pipeline, why is “artifact versioning” important? A. To ensure each build can be uniquely identified and reproduced. B. To hide changes from auditors. C. To reduce storage costs. D. To avoid using containers. Answer: A Explanation: Versioned artifacts enable traceability and reproducibility. Question 44. Which of the following best describes “Canary Analysis” in a deployment pipeline? A. Randomly selecting a server to deploy. B. Comparing metrics of a small rollout against baseline to decide full release. C. Deploying to all users simultaneously.
Answer: B Explanation: Latency measures the time taken to respond to a request. Question 48. What is the primary advantage of using “Blue‑Green” over “Canary” deployments? A. Zero downtime with instant rollback. B. Gradual exposure to users. C. No need for duplicate environments. D. Requires no testing. Answer: A Explanation: Blue‑Green swaps entire environments, enabling instant rollback with no downtime. Question 49. In the context of DevOps, “ChatOps” refers to: A. Using chat platforms to automate operational tasks via bots. B. Replacing all documentation with instant messaging. C. Conducting code reviews over video calls. D. Deploying code through SMS. Answer: A Explanation: ChatOps integrates chat tools with automation for operational commands. Question 50. Which of the following is a key characteristic of a “high‑trust” DevOps culture? A. Strict hierarchical approvals. B. Open sharing of failures and learning. C. Limited access to production. D. Isolated development silos.
Answer: B Explanation: High‑trust cultures encourage transparency and learning from mistakes. Question 51. Which of these tools is primarily used for continuous integration in a Java ecosystem? A. Maven. B. Docker. C. Ansible. D. Terraform. Answer: A Explanation: Maven can automate builds and run tests, serving CI needs for Java. Question 52. When implementing IaC, which language is associated with Terraform? A. YAML. B. HCL (HashiCorp Configuration Language). C. JSON. D. Ruby. Answer: B Explanation: Terraform uses HCL to define infrastructure resources. Question 53. Which of the following best describes “Feature Toggles”? A. A method to permanently remove code. B. A technique to enable/disable functionality at runtime. C. A way to increase code complexity. D. A security vulnerability scanner. Answer: B
Question 57. The “Testing Pyramid” suggests that as you move up the pyramid, tests become: A. Faster and more numerous. B. Slower and fewer in number. C. More manual. D. Irrelevant. Answer: B Explanation: Higher‑level tests (integration, UI) are slower and fewer compared to unit tests. Question 58. Which of the following best illustrates “continuous delivery” in practice? A. Deploying code to production once a year. B. Automatically building, testing, and staging code ready for release at any time. C. Manually copying files to servers. D. Skipping automated tests to speed up releases. Answer: B Explanation: Continuous Delivery ensures every change is production‑ready after automated validation. Question 59. Which of these statements about “GitOps” is true? A. It replaces Git with a proprietary VCS. B. Operational state is stored declaratively in Git and applied automatically. C. It discourages version control for infrastructure. D. It only applies to front‑end development. Answer: B Explanation: GitOps uses Git as the source of truth for both application and infrastructure configurations.
Question 60. In the context of DevOps metrics, a “low change failure rate” indicates: A. Frequent production outages. B. High stability of releases. C. Slow deployment speed. D. Large batch sizes. Answer: B Explanation: Fewer failures per change imply more stable releases. Question 61. Which of the following is a primary benefit of “immutable infrastructure”? A. Ability to patch live servers manually. B. Consistency across environments by never modifying running instances. C. Reduced need for monitoring. D. Increased reliance on manual configuration. Answer: B Explanation: Immutable infrastructure replaces instances rather than updating them, ensuring consistency. Question 62. Which tool is commonly used for container image scanning for vulnerabilities? A. SonarQube. B. Clair. C. Nagios. D. Jenkins. Answer: B Explanation: Clair scans Docker images for known security issues.