Microservices Architecture and Deployment GCSA Practice Questions (Page 6)

Questions 26–30

1. 26expert · hard

   A company is refactoring a monolithic application into microservices. The team wants to ensure that each service can be developed, deployed, and scaled independently. They also want to avoid sharing a single database schema across services. Which architectural principle should they follow?

   • AService-to-service direct database access
   • BDecentralized data management
   • CShared in-memory cache
   • DCentralized database with shared schema
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A development team is containerizing a microservice that reads configuration from environment variables. They want to ensure that the same container image can be promoted from development to production without rebuilding, and that secrets are not baked into the image. Which approach should they use?

   • AEmbed configuration in the image using build arguments and store secrets in the image registry
   • BStore configuration in a ConfigMap and secrets in a Secret, and mount them as environment variables at runtime
   • CUse a single environment variable file that is copied into the image during the build
   • DSet environment variables in the container runtime and store secrets in the image label
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   An online payment service is deploying a new version of its transaction-processing microservice. The team wants to minimize the risk of a faulty release affecting all users while still being able to quickly roll back if problems occur. They have the ability to route traffic based on HTTP headers and can run multiple versions of the service simultaneously. Which deployment strategy best fits these requirements?

   • ARecreate deployment
   • BBlue-green deployment
   • CCanary deployment
   • DRolling deployment
   Reveal Solution Discussion Select an answer first
5. 29expert · hard

   A team is setting up a CI/CD pipeline for a microservice that is deployed to a Kubernetes cluster. They want to automatically deploy to production only if the service passes integration tests and a security scan. They also want to be able to roll back quickly if the deployment causes issues. Which pipeline design should they use?

   • APipeline that deploys to production using a rolling update, and runs tests after deployment
   • BPipeline that deploys directly to production after a build, and relies on monitoring to detect issues
   • CPipeline that uses a canary deployment, but only after running unit tests, without a security scan
   • DPipeline with stages: build, test, scan, deploy to staging, run integration tests, then deploy to production using a blue-green strategy
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A company has a microservices architecture with many services. They are experiencing intermittent failures in one service, and they need to identify which service is causing a slowdown in a user request that spans multiple services. Which observability practice should they implement?

   • AHealth checks that verify each service is running
   • BMetrics collection with a dashboard showing CPU and memory usage per service
   • CCentralized logging with each service writing to a separate log file
   • DDistributed tracing with a correlation ID propagated across service calls
   Reveal Solution Discussion Select an answer first