Understanding the DevOps Workflow GCSA Practice Questions (Page 5)

Questions 21–25

1. 21expert · hard

   A team uses Git for version control. They want to enforce that every change to application code and infrastructure is reviewed by at least one other person before it is merged. They also want to ensure that the CI pipeline runs on the merged code, not just on the branch. Which Git workflow best achieves this?

   • AUse a single shared branch where all developers commit and run CI locally before pushing.
   • BAllow developers to push directly to the main branch and rely on post-merge CI to catch issues.
   • CUse a feature branch workflow with pull requests and branch protection rules that require a review and a successful CI check before merging.
   • DUse Git tags to mark releases and require reviews only for tagged commits.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A team is migrating a monolithic application to microservices. They want to maintain the ability to deploy a fix for one service without redeploying other services. They also want to minimize the risk of a bad deployment affecting all users. Which deployment strategy best meets these requirements?

   • ADeploy each microservice independently using a blue/green deployment strategy with automated rollback.
   • BUse a rolling deployment that updates all microservices in a fixed order.
   • CUse a canary deployment for the entire application, releasing the new version to a small percentage of users.
   • DDeploy all microservices together as a single release to ensure consistency across services.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   What is the purpose of a feedback loop in DevOps?

   • ATo replace the need for automated testing
   • BTo ensure that code is never deployed to production
   • CTo automate the approval of release requests
   • DTo provide information that helps teams improve quality and performance
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   A team deploys a new version of a service. The deployment pipeline reports success, but users begin reporting errors. The team suspects the new version has a bug that was not caught by tests. They want to confirm the cause and prevent similar issues in the future. Which combination of monitoring and pipeline changes would be most effective?

   • AAdd structured logging and metrics to the service, create a dashboard that correlates deployment time with error rate, and add a canary deployment stage that automatically rolls back if error rate spikes.
   • BReview the application logs manually after each deployment and document any anomalies in a post-mortem report.
   • CIncrease the number of unit tests in the CI pipeline to catch all possible bugs before deployment.
   • DDisable the deployment pipeline and require all changes to be deployed manually after a two-week testing period.
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A DevOps team is selecting tools for their CI/CD pipeline. They need a tool that can orchestrate complex workflows, integrate with multiple cloud providers, and support infrastructure as code. They also want to minimize the number of tools they need to maintain. Which tool should they choose?

   • AA container orchestration tool like Kubernetes.
   • BA configuration management tool like Ansible.
   • CJenkins with plugins for cloud providers and IaC tools.
   • DA cloud provider's native CI/CD service, such as AWS CodePipeline.
   Reveal Solution Discussion Select an answer first