Understanding the DevOps Workflow GCSA Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   What is the key difference between continuous delivery and continuous deployment?

   • AContinuous delivery ensures code is always ready for release, while continuous deployment automatically releases every change to production
   • BContinuous delivery automates releases to production, while continuous deployment requires manual approval
   • CContinuous delivery is a manual process, while continuous deployment is automated
   • DContinuous delivery is only for infrastructure, while continuous deployment is for applications
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A company is moving from a monolithic application to a microservices architecture. They want to use containers and Kubernetes for deployment. However, they are concerned about the complexity of managing multiple services and want to ensure that infrastructure changes are versioned and reproducible. Which combination of practices best addresses their concerns?

   • AUse Docker Compose to manage all services and deploy manually to each environment.
   • BUse a configuration management tool like Ansible to configure each container after it is deployed.
   • CUse a cloud provider's managed Kubernetes service and manually create resources through the console.
   • DUse Kubernetes manifests stored in Git and apply them with a GitOps tool like Argo CD.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   Which type of automated test focuses on testing individual components in isolation?

   • AIntegration test
   • BUnit test
   • CLoad test
   • DEnd-to-end test
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   An e-commerce platform deploys new code multiple times per day. After a recent deployment, customers reported slow page loads, but the development team was not aware until the next day. The team wants to detect performance regressions immediately after each deployment. Which action should they take?

   • AAdd a synthetic monitoring check that measures page load time and triggers an alert if it exceeds a threshold.
   • BReview the application logs manually at the end of each day to identify slow requests.
   • CAsk the support team to report any customer complaints about performance.
   • DIncrease the number of application instances to handle the load.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A team wants to implement continuous deployment for a low-risk internal tool. They are concerned about the impact of a bad deployment on users. They want to balance the speed of automated deployment with the ability to limit the blast radius. Which strategy should they use?

   • ADeploy to a staging environment and require a human to manually promote to production.
   • BDeploy to all users at once and rely on the monitoring dashboard to detect issues.
   • CDeploy to production only during off-peak hours and monitor for a day before considering it successful.
   • DDeploy to a small percentage of users first (canary) and automatically roll back if error rate increases, then gradually increase the percentage.
   Reveal Solution Discussion Select an answer first