Cloud Digital Leader Why Cloud Technology Can Transform Business Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Cloud Service Mesh (or Istio)

  Why this is correct

  Cloud Service Mesh (Istio) injects Envoy sidecar proxies into each pod, creating a data plane that intercepts and controls east-west traffic between microservices. It provides mutual TLS, traffic splitting, retries, and rich telemetry, while the control plane manages policies via custom resource definitions. Because it operates transparently at the application layer, teams can enforce security and reliability without modifying service code.

• ✓

  Google Kubernetes Engine (GKE)

  Why this is correct

  Google Kubernetes Engine (GKE) serves as the managed Kubernetes control plane and worker pool that schedules, scales, and heals containerized microservices. It automates rolling deployments, self-heals failed pods, and exposes services via ClusterIP, NodePort, and LoadBalancer types, making it the runtime foundation for a microservices platform. However, GKE alone does not offer the L7 policy and observability features that a service mesh layer provides.

• ✗

  Cloud Storage

  Why it's wrong here

  Cloud Storage is a fully managed object store for immutable binary data such as media files, database backups, and data lake archives, with no compute or traffic-routing capabilities. It cannot execute containers, host long-running processes, or mediate requests between services. While microservices may use it to persist static assets or transaction logs, it is not a communication or orchestration plane and therefore cannot modernize the application's runtime.

• ✓

  Cloud Load Balancing

  Why this is correct

  Cloud Load Balancing is a distributed, anycast-based L4/L7 service that routes incoming user traffic to healthy backend microservice instances across regions, enabling high availability and automatic scaling. It terminates SSL, applies URL-based routing, and integrates with GKE ingress controllers, but it only manages north-south (external to service) traffic, not intra-cluster service-to-service calls.

• ✗

  Cloud Functions

  Why it's wrong here

  Cloud Functions is a serverless FaaS offering that runs short-lived, event-triggered code (e.g., HTTP endpoints or Pub/Sub handlers) with a default timeout of 60 seconds and a maximum of 540 seconds, designed for stateless, burstable workloads. It lacks support for persistent connections, service discovery, and sidecar injection, so it cannot sustain the long-running, stateful interactions of a monolithic microservice decomposition. Its per-invocation concurrency and scaling model also make it unsuitable as a general-purpose microservice host.

Go deeper

Related to this question