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 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?
This option involves deploying the full Apigee hybrid runtime plane, which installs Kubernetes-based runtime microservices, ingress gateways, message processors, and an on-premises Apache Cassandra cluster for state storage.
While Apigee hybrid keeps runtime traffic on-premises and provides full API governance, a complete deployment has a substantial infrastructure footprint. The requirement explicitly states that the enterprise must avoid the operational overhead and high resource cost of managing full runtime clusters and stateful datastores locally.
The organization required advanced monetization policies, local message transformations, complex custom Java/Python callouts, and had dedicated infrastructure teams capable of maintaining high-availability on-premises Cassandra clusters.
This design implements a centralized cloud gateway architecture where on-premises clients route internal API calls over Cloud Interconnect or Cloud VPN into a Google Cloud-hosted Apigee instance, which inspects the request and forwards it back on-premises to the legacy backend (a pattern known as hair-pinning).
Routing traffic from an on-premises client to Google Cloud and back down to an on-premises legacy server introduces significant network latency, network egress costs, and potential bottlenecks. It violates the constraint to keep data plane processing close to local workloads.
The API callers were external internet consumers or purely cloud-native applications hosted in Google Cloud accessing on-premises backends.
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.
This approach uses Cloud Pub/Sub messaging queues and event listeners as an intermediary buffer to decouple legacy systems from cloud services asynchronously.
While asynchronous messaging is a core pattern for event-driven integration, it is not a direct substitute for synchronous REST API management. Pub/Sub does not provide native API key validation, synchronous quota enforcement, or standard HTTP API analytics dashboards that are central to Apigee gateway functionality.
The primary goal was batch data ingestion, asynchronous decoupling of event-driven event streams, or background job processing where real-time synchronous HTTP responses are not required.
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