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 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:
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.
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 a complete Apigee hybrid runtime plane including Cassandra datastores and message processors across the on-premises data center clusters.
Deploy Apigee Adapter for Envoy on-premises to enforce security and quotas locally, while connecting asynchronously to the Google Cloud Apigee management plane.
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.
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.
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 a complete Apigee hybrid runtime plane including Cassandra datastores and message processors across the on-premises data center clusters.