<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mcq on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/categories/mcq/</link><description>Recent content in Mcq on Ghafoor's Personal Blog</description><generator>Hugo</generator><language>en</language><managingEditor>noreply@example.com (AG Sayyed)</managingEditor><webMaster>noreply@example.com (AG Sayyed)</webMaster><copyright>Copyright © 2024-2026 AG Sayyed. All Rights Reserved.</copyright><lastBuildDate>Fri, 15 May 2026 13:20:20 +0100</lastBuildDate><atom:link href="http://ghafoorsblog.com/categories/mcq/index.xml" rel="self" type="application/rss+xml"/><item><title>Module Mcq</title><link>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/01-introduction-to-devops/03-module/007-module-mcq/</link><pubDate>Sun, 25 May 2025 14:12:28 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/01-introduction-to-devops/03-module/007-module-mcq/</guid><description>&lt;h2 id="module-3-multiple-choice-questions"&gt;Module-3 Multiple Choice Questions&lt;/h2&gt;

 

&lt;div class="accordion" id="mcqAccordion"&gt;
 &lt;div class="accordion-item"&gt;
 &lt;h2 class="accordion-header" id="headingOne"&gt;
 &lt;button
 class="accordion-button collapsed"
 type="button"
 data-bs-toggle="collapse"
 data-bs-target="#collapseOne"
 aria-expanded="false"
 aria-controls="collapseOne"&gt;
 Multiple Choice Questions And Answers
 &lt;/button&gt;
 &lt;/h2&gt;
 &lt;div
 id="collapseOne"
 class="accordion-collapse collapse"
 aria-labelledby="headingOne"
 data-bs-parent="#mcqAccordion"&gt;
 &lt;div class="accordion-body"&gt;
 &lt;div class="progress"&gt;
 &lt;div
 id="progress-bar"
 class="progress-bar"
 role="progressbar"
 style="width: 0%;"
 aria-valuenow="0"
 aria-valuemin="0"
 aria-valuemax="100"&gt;&lt;/div&gt;
 &lt;/div&gt;

 &lt;div id="mcq-container"&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Software development is creative and collaborative, not an assembly line."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which of the following best explains why Taylorism is unsuitable for modern software development?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Software development requires repetitive manual tasks.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Software development is creative and collaborative, not an assembly line.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Taylorism encourages automation and innovation.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Taylorism reduces the need for team communication.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Bottlenecks, miscommunication, and project delays."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the most likely outcome if a software team continues to work in silos, as described by Taylorism?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Increased collaboration and faster delivery.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Bottlenecks, miscommunication, and project delays.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Higher code quality due to specialization.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. More innovation from isolated teams.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="3. Frequent, small releases with automation."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which practice is essential for enabling rapid feedback and minimizing risk in DevOps?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Large, infrequent releases.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Manual handoffs between teams.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Frequent, small releases with automation.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Strict command-and-control management.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Lack of ownership and understanding of the software."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the most likely effect of treating software engineering like civil engineering?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Improved adaptability to change.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Lack of ownership and understanding of the software.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Faster delivery of new features.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Continuous product improvement.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Retaining the same team for development and maintenance."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which approach leads to higher-quality software in the long term?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Treating software as a one-time project with handoffs.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Retaining the same team for development and maintenance.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Using only manual testing.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Avoiding updates after release.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Breaking down silos and fostering shared ownership."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which behavior is most critical for a successful DevOps organization?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Maintaining strict separation between development and operations.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Breaking down silos and fostering shared ownership.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Relying on manual change review boards.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Building bespoke infrastructure for each deployment.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Consistency and reproducibility through automation."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the primary benefit of Infrastructure as Code (IaC)?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Manual configuration of servers.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Consistency and reproducibility through automation.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Increased server drift over time.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Reduced use of version control.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Environments are quickly created and destroyed as needed."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which scenario best illustrates the use of ephemeral infrastructure?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Servers are manually updated and maintained for years.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Environments are quickly created and destroyed as needed.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. All infrastructure changes are made directly on production.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Only one environment exists for all testing and production.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Increased risk of integration issues and production failures."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the most likely outcome if a team does not use automated testing in their CI/CD pipeline?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Higher code quality and fewer bugs.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Increased risk of integration issues and production failures.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Faster deployment cycles.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. More reliable releases.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Updates are made by replacing old components with new ones."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which of the following best describes the principle of immutable delivery?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Infrastructure components are modified after deployment.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Updates are made by replacing old components with new ones.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Manual changes are allowed in production.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Only one version of infrastructure is maintained.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Committing frequently in small batches."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which practice helps reduce the risk of merge conflicts in a CI/CD workflow?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Working in large, long-lived branches.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Committing frequently in small batches.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Avoiding code reviews.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Merging untested code into the master branch.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Elimination of manual ticket queues and faster delivery."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the most likely benefit of using automated self-service in DevOps?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Slower provisioning of environments.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Elimination of manual ticket queues and faster delivery.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Increased manual intervention.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. More errors due to lack of automation.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Improved collaboration and shared goals."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which of the following is a direct result of breaking down silos in a DevOps team?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Increased handoffs and miscommunication.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Improved collaboration and shared goals.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. More bottlenecks in the workflow.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Reduced innovation due to micromanagement.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Increased risk of major failures and slow recovery."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 If a software team only pushes large, infrequent releases, what is the most likely risk?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Faster feedback and learning.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Increased risk of major failures and slow recovery.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Reduced need for testing.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. More opportunities for automation.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. It encourages creativity and tailored solutions."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Why is treating software development as craftwork important?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. It allows for strict process control.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. It encourages creativity and tailored solutions.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. It reduces the need for team collaboration.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. It makes software development identical to factory work.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="1. Civil engineering projects rarely change after completion, while software requires ongoing updates."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which of the following best describes the difference between civil engineering and software engineering?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Civil engineering projects rarely change after completion, while software requires ongoing updates.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Software engineering is always static.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Civil engineering is more dynamic than software engineering.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Both fields follow the same project management model.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. It leads to a lack of understanding and ownership of the code."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is a key flaw in the traditional project management model for software?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. It fosters continuous ownership and improvement.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. It leads to a lack of understanding and ownership of the code.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. It encourages stable, long-lasting teams.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. It supports frequent updates and enhancements.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Empowering teams to provision resources automatically."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which behavior is essential for enabling automated self-service in DevOps?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Manual ticket queues for every request.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Empowering teams to provision resources automatically.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Relying on change review boards.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Building unique, hand-crafted infrastructure.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Environments can be quickly created and destroyed, reducing costs."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the main advantage of using ephemeral infrastructure in deployments?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Servers are never replaced.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Environments can be quickly created and destroyed, reducing costs.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Manual updates are easier.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Infrastructure is always unique.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Consistency and traceability of infrastructure changes."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which of the following is a benefit of storing Infrastructure as Code in version control?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Changes are undocumented.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Consistency and traceability of infrastructure changes.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Increased server drift.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Reduced collaboration.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. To continuously build, test, and integrate changes for early detection of issues."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the primary goal of continuous integration?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. To delay testing until the end of the project.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. To continuously build, test, and integrate changes for early detection of issues.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. To merge untested code into the master branch.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. To avoid code reviews.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Frequent automated testing and code reviews."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which practice helps ensure the master branch is always deployable?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Merging untested code.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Frequent automated testing and code reviews.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Working in isolation for long periods.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Avoiding pull requests.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Ensuring every change can be released to production at any time."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is a key principle of continuous delivery?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Deploying only once a year.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Ensuring every change can be released to production at any time.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Manual deployments without automation.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Avoiding feedback loops.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Using feature flags and gradual rollouts."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Which risk management technique is commonly used in continuous deployment?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Deploying all changes at once without testing.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Using feature flags and gradual rollouts.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Manual updates in production.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Avoiding automation.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. It reduces errors and speeds up delivery."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 Why is automation important in DevOps and CI/CD pipelines?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. It increases manual intervention.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. It reduces errors and speeds up delivery.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. It makes deployments less reliable.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. It eliminates the need for testing.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div
 class="card mcq-card"
 style="display: none;"
 data-answer="2. Reduces risk and simplifies testing."&gt;
 &lt;div class="card-body"&gt;
 &lt;h5 class="card-title"&gt;
 &lt;span class="question-number"&gt;&lt;/span&gt;
 What is the benefit of working in small batches in software development?
 &lt;/h5&gt;
 &lt;ul class="list-group list-group-flush"&gt;
 &lt;li class="list-group-item"&gt;
 1. Increases the risk of merge conflicts.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 2. Reduces risk and simplifies testing.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 3. Delays feedback.
 &lt;/li&gt;
 &lt;li class="list-group-item"&gt;
 4. Makes code reviews harder.
 &lt;/li&gt;
 &lt;/ul&gt;
 &lt;div class="feedback-box mt-3" style="display: none;"&gt;
 &lt;div class="alert alert-info"&gt;
 &lt;strong&gt;Explanation:&lt;/strong&gt;
 &lt;span class="feedback-text"&gt;&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;

 &lt;div class="d-flex justify-content-between align-items-center"&gt;
 &lt;button id="next-button" class="btn btn-primary"&gt;Next&lt;/button&gt;
 &lt;button
 id="start-over-button"
 class="btn btn-secondary"
 style="display: none;"&gt;
 Start Over
 &lt;/button&gt;
 &lt;/div&gt;

 &lt;div id="score" class="mt-3"&gt;
 Attempted Questions: 0 /
 26
 &lt;/div&gt;
 &lt;div id="summary-container" class="mt-4"&gt;&lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
&lt;/div&gt;



&lt;script&gt;
window.HUGO_ENVIRONMENT = "production";
&lt;/script&gt;</description></item></channel></rss>