Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An e-commerce company is modernizing its application architecture. External web and mobile clients communicate using public RESTful HTTPS APIs with JSON payloads. However, the internal backend microservices have been developed using high-performance gRPC over HTTP/2. Additionally, heavy read traffic for product catalog data is placing unnecessary load on backend services and increasing response latency for end users.
You need to advise the development and operations teams on an API mediation and performance optimization strategy that decouples the clients from backend services, performs protocol translation, and minimizes backend load.
Which architectural solution should you recommend?
A Passthrough Network Load Balancer (regional or global) operates at Layer 4 (TCP/UDP) of the OSI model. It distributes incoming IP packets directly to healthy backend virtual machines or containers without inspecting, terminating, or modifying application-layer payload data.
You required ultra-high throughput Layer 4 TCP load balancing with direct server return for clients that already natively speak gRPC directly to the backend servers.
An API management mediation layer (such as Apigee) serves as an enterprise gateway and abstraction facade between external consumers and internal backend microservices. It intercepts incoming client requests, executes governance, routing, and message mediation policies, and translates communication protocols and data payloads between disparate architectures.
Placing an API management proxy at the edge of the microservices ecosystem achieves both architectural isolation and significant performance improvements. Backend engineering teams retain the freedom to optimize internal services with gRPC without forcing external clients to adopt gRPC tooling or manage protocol compatibility.
This approach involves redesigning backend microservices to remove gRPC interfaces and replace them with standard HTTP/1.1 REST endpoints, handling JSON encoding, serialization, and decoding within the application code of each individual microservice.
The backend services were simple legacy web applications where gRPC brought unnecessary operational overhead and no performance benefits were required.
Proxyless gRPC allows applications with integrated gRPC client libraries to communicate directly with backend gRPC servers using xDS APIs provided by Cloud Service Mesh. It eliminates the resource overhead and latency of sidecar proxies by letting the gRPC library handle service discovery, load balancing, and regional failover natively.
xds:/// name resolution schemes configured directly inside client application channels.You were designing high-performance internal microservice-to-microservice communication inside a Google Cloud Virtual Private Cloud where every millisecond of sidecar latency needed to be eliminated.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated