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.
A financial enterprise runs a distributed microservices application inside an on-premises Kubernetes cluster managed with an Istio service mesh. The enterprise needs to expose several services to partner developers while implementing centralized API governance.
The solution must satisfy the following architectural requirements:
Which solution should the cloud architect recommend?
Apigee Adapter for Envoy is an API gateway integration solution that combines the lightweight proxy capabilities of Envoy (and Istio) with the centralized governance and analytics features of the Apigee platform. It allows organizations to deploy a lightweight data plane directly adjacent to backend services while maintaining centralized management in Google Cloud.
Disabling sidecar injection (using sidecar.istio.io/inject="false") bypasses the service mesh proxy, requiring developers to write custom authentication, rate limiting, and telemetry logic directly into each individual microservice codebase.
This approach eliminates centralized governance and fails to provide integration with Apigee Analytics dashboards, API key validation systems, or unified quota management. Furthermore, embedding security logic directly into applications creates code duplication, inconsistent security enforcement across microservices, and substantial maintenance overhead.
A service required high-performance, non-standard UDP protocols that cannot be processed by Layer 7 proxies or if a legacy application could not operate with sidecar traffic redirection.
Apigee X is Google Cloud's fully managed, cloud-native API management platform, where both the management plane and runtime plane operate within Google-managed VPC networks.
Routing local on-premises consumer traffic out to Google Cloud and back down via an external Cloud Load Balancer introduces significant network latency and violates the requirement to maintain traffic boundaries within the on-premises data center. Sending internal or localized partner API calls over hybrid network links adds serialization latency, egress costs, and points of failure.
The workloads were fully hosted in Google Cloud Virtual Private Clouds (VPCs) or if external public internet consumers were accessing cloud-native backends.
Apigee hybrid is an enterprise deployment model where the API management runtime plane is installed on customer-managed Kubernetes infrastructure (either on-premises or in other clouds), while the management plane remains hosted in Google Cloud.
While Apigee hybrid keeps runtime traffic within the on-premises boundary, deploying a full hybrid runtime involves provisioning and maintaining heavy data storage layers (such as Apache Cassandra), distributed message processors, and persistent volume management. The scenario explicitly requires avoiding the resource overhead and operational complexity associated with hosting a full on-premises runtime deployment.
The organization required full enterprise runtime policies (such as complex Java/JavaScript callouts, local monetization engines, or extensive XML/JSON payload transformations) and had dedicated infrastructure teams to manage the stateful runtime cluster.
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