Microservices Architecture and Deployment GCSA Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   A company is migrating a monolithic application to microservices. The team wants to ensure that each microservice can be developed, deployed, and scaled independently. They also want to avoid a single point of failure in the database. Which architectural principle should they apply?

   • ADecentralized data management, where each service owns its own database or data store
   • BUse a distributed transaction manager to coordinate all database operations
   • CAPI-based communication with a shared data layer
   • DCentralized data management, where all services share a single database
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A microservice that processes orders is experiencing occasional timeouts when calling a downstream inventory service. The team wants to prevent the order service from being overwhelmed by repeated failures and to provide a fallback response when the inventory service is unavailable. Which pattern should they implement?

   • AIncrease the timeout on the HTTP client
   • BUse a load balancer to distribute requests to multiple inventory service instances
   • CCircuit breaker with a fallback method that returns a cached inventory count
   • DRetry with exponential backoff and jitter
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A company runs a microservices application on Kubernetes. The frontend service needs to call the backend service, but the backend service has multiple replicas that are dynamically created and destroyed. The frontend must always reach a healthy backend instance. Which mechanism should they use?

   • AA Kubernetes Service with a selector that matches the backend pods, and a readiness probe on the backend pods
   • BA headless Service with no selector, and the frontend uses the pod IPs directly
   • CAn ExternalName Service that points to an external load balancer
   • DA ConfigMap that lists the backend pod IPs, updated manually whenever pods change
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A company is rolling out a microservices-based customer portal. The portal must authenticate users centrally, route requests to the correct service, and enforce per-client API call limits. The security team requires that service-to-service communication be encrypted and mutually authenticated, but they do not want to manage individual TLS certificates for each service. Which combination of components should the company implement?

   • AAPI gateway with JWT validation, and a centralized TLS termination proxy for all east-west traffic
   • BService mesh with mTLS, and a load balancer that performs authentication and rate limiting
   • CAPI gateway with client certificates for every service, and a network policy that restricts traffic to the gateway
   • DAPI gateway with OIDC, service mesh with mTLS, and a sidecar proxy for each service
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A security team is designing a microservices deployment on Kubernetes. They need to ensure that only the frontend service can communicate with the backend service, and that all service-to-service communication is encrypted. They also need to ensure that the backend service cannot access the internet. Which set of controls should they implement?

   • AA single network policy that blocks all egress from the backend, and rely on the API gateway for encryption
   • BUse a private container registry and only allow images from that registry
   • CNetwork policies that allow ingress to the backend only from the frontend, and a service mesh with mTLS
   • DImplement mTLS using self-signed certificates and manually distribute them to each service
   Reveal Solution Discussion Select an answer first