Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Configure a Passthrough Network Load Balancer with TCP health checks to route client JSON requests directly to backend gRPC container endpoints.
Deploy direct proxyless gRPC client libraries onto all external client devices and configure Cloud Service Mesh using xDS name resolution.
Refactor backend microservices to natively serve REST/JSON over HTTP/1.1 and disable service discovery and connection pooling.
Implement an API management mediation layer (such as Apigee) that exposes RESTful JSON endpoints to clients, translates requests to gRPC backend microservices, and applies response caching policies for read requests.
Configure a Passthrough Network Load Balancer with TCP health checks to route client JSON requests directly to backend gRPC container endpoints.
Deploy direct proxyless gRPC client libraries onto all external client devices and configure Cloud Service Mesh using xDS name resolution.
Refactor backend microservices to natively serve REST/JSON over HTTP/1.1 and disable service discovery and connection pooling.
Implement an API management mediation layer (such as Apigee) that exposes RESTful JSON endpoints to clients, translates requests to gRPC backend microservices, and applies response caching policies for read requests.
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.
StudyCerts
StudyCerts