Understanding the DevOps Workflow GCSA Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A company is migrating a monolithic application to a microservices architecture on Kubernetes. They want to manage the infrastructure and application configuration using the same DevOps workflow as their code. Which practice should they adopt?

   • ACreate a separate environment for each microservice and manage them manually.
   • BUse a container registry to store all microservice images and deploy them manually.
   • CUse a configuration management tool like Ansible to configure each microservice individually after deployment.
   • DStore Kubernetes manifests in a Git repository and apply them through a CI/CD pipeline.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A company has adopted DevOps tools but still experiences frequent deployment failures. The development team writes code, and the operations team manually configures the production environment. They want to improve reliability. Which change would most directly address the root cause of the failures?

   • AHave the operations team run the CI pipeline after the development team finishes coding.
   • BCreate a detailed handoff document that describes the production environment configuration.
   • CHave the development team use infrastructure as code to define the production environment, and have operations review the changes through the same version control workflow.
   • DIncrease the number of operations staff to handle the manual configuration more quickly.
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A company uses Terraform to manage its AWS infrastructure. The Terraform state file is stored locally on a developer's laptop. After a recent incident, the team discovered that two developers applied conflicting changes, and the state file became corrupted. They want to prevent this and also enable automated deployments. Which change should they make?

   • AUse a local state file but create a backup after every apply.
   • BStore the Terraform state file in a remote backend such as S3 with DynamoDB locking, and run Terraform apply only from the CI/CD pipeline.
   • CStore the state file in a Git repository and have developers pull before applying.
   • DKeep the state file locally but require developers to take turns applying changes manually.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A team is building a CI/CD pipeline for a critical application. They have a limited budget for CI minutes and want to maximize the chance of catching defects before production. They have three test suites: unit tests (2 minutes), integration tests (10 minutes), and end-to-end tests (30 minutes). The team wants to run the pipeline on every commit, but the total time must stay under 15 minutes. Which testing strategy should they use?

   • ARun unit tests and integration tests on every commit, and run end-to-end tests only on merges to main.
   • BRun only end-to-end tests on every commit, and skip unit and integration tests.
   • CRun all three test suites on every commit, but only for the main branch.
   • DRun only unit tests on every commit, and run integration and end-to-end tests only in a nightly job.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   Why is version control important for infrastructure as code?

   • AIt eliminates the need for testing infrastructure code
   • BIt encrypts infrastructure configuration files
   • CIt automatically deploys infrastructure changes
   • DIt provides a history of infrastructure changes and enables rollback
   Reveal Solution Discussion Select an answer first