An enterprise is planning a phased migration of its core legacy applications from an on-premises data center to Google Cloud. The architecture team needs to establish an API management layer to facilitate interoperability between legacy backends and newly migrated cloud services. The proposed integration architecture must satisfy the following constraints: Provide API key verification, quota management, and centralized analytics managed through Apigee in Google Cloud. Minimize latency for local service-to-service communication by keeping data plane processing close to the on-premises legacy workloads. Avoid the operational complexity and large resource footprint of hosting a full Apigee runtime stack and local data stores on-premises. Which architectural pattern should you implement to satisfy these requirements?

Deploy Apigee Adapter for Envoy on-premises to enforce security and quotas locally, while connecting asynchronously to the Google Cloud Apigee management plane.: ### What Apigee Adapter for Envoy is **Apigee Adapter for Envoy** is an API gateway solution that uses the open-source **Envoy proxy** coupled with an **Apigee Remote Service** to provide policy enforcement and API governance in close proximity to backend services. ### How it meets the requirements - **Low Latency & Data Residency**: By placing the lightweight **Envoy data plane** directly in the on-premises environment alongside legacy applications, incoming requests are evaluated and proxied locally without hair-pinning traffic to Google Cloud. - **Centralized Apigee Governance**: The **Apigee Remote Service** acts as a **Policy Decision Point (PDP)** to validate **API keys**, enforce **quotas**, and authenticate tokens against policies downloaded from the **Apigee management plane** hosted in Google Cloud. - **Small Operational Footprint**: Unlike a full on-premises runtime deployment, the Envoy adapter does not require heavy local components like distributed datastores or complete analytics processors, significantly reducing infrastructure complexity. ### Key advantages and capabilities - **Asynchronous Telemetry**: Captures and transmits **API analytics** data to Google Cloud asynchronously without adding request overhead or latency. - **Resilience to Network Glitches**: The adapter caches verification data and tolerates transient disconnections from the cloud management plane while continuing to serve traffic. - **Standardized Proxy Layer**: Seamlessly integrates into existing service mesh architectures (such as Istio) or standalone virtual machine workloads. ### Why this is optimal This pattern provides the ideal balance between centralized enterprise governance (via Google Cloud-hosted Apigee) and local, low-latency execution with a minimal compute footprint on-premises.

StudyCerts

Apigee Adapter Envoy Hybrid Integration | 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! | StudyCerts

Professional Cloud Architect

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!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Apigee Adapter Envoy Hybrid Integration

Section: Integrating solutions with existing systems

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.

An enterprise is planning a phased migration of its core legacy applications from an on-premises data center to Google Cloud. The architecture team needs to establish an API management layer to facilitate interoperability between legacy backends and newly migrated cloud services.

The proposed integration architecture must satisfy the following constraints:

Provide API key verification, quota management, and centralized analytics managed through Apigee in Google Cloud.
Minimize latency for local service-to-service communication by keeping data plane processing close to the on-premises legacy workloads.
Avoid the operational complexity and large resource footprint of hosting a full Apigee runtime stack and local data stores on-premises.

Which architectural pattern should you implement to satisfy these requirements?

Implement an asynchronous Pub/Sub buffer between legacy applications and cloud services using on-premises connectors for synchronous REST API calls.

Route all on-premises legacy traffic across Cloud Interconnect to an external HTTP(S) Load Balancer and Apigee cloud proxy before routing it back on-premises.

Deploy Apigee Adapter for Envoy on-premises to enforce security and quotas locally, while connecting asynchronously to the Google Cloud Apigee management plane.

Deploy a complete Apigee hybrid runtime plane including Cassandra datastores and message processors across the on-premises data center clusters.

Professional Cloud Architect

Apigee Adapter Envoy Hybrid Integration

Related questions