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 e-commerce company hosts an order submission system on Google Cloud. During marketing flash sales, order submission traffic increases tenfold.
Currently, the frontend microservice synchronously calls an external legacy third-party inventory and payment verification system for each submitted order. The legacy system has strict throughput limitations, does not scale elastically, and responds with high latency under load. Consequently, during traffic spikes, frontend connection pools become exhausted, requests time out, and customer orders fail.
The architecture must meet the following requirements:
Which integration architecture should you implement?
Archive Deployment in Apigee is a deployment mechanism designed for local API proxy development and testing using Cloud Code and the Apigee Emulator. It allows developers to package proxy configurations into an archive and deploy them into Apigee environments configured specifically for declarative, local development workflows.
A development team needed to run repeatable proxy unit tests and automated continuous integration cycles within a local workstation environment without impacting shared environments.
Confusing local testing emulators with production scaling mechanisms is a common architectural misconception. Production scalability requires architectural decoupling rather than development-time emulator tooling.
This architecture combines Apigee API Management with Cloud Pub/Sub asynchronous messaging to decouple frontend intake from downstream processing. Apigee acts as the API gateway providing entry governance, security, and traffic shaping, while Cloud Pub/Sub serves as a distributed, highly scalable buffer that temporarily persists incoming order messages until backend consumers are ready to process them.
Synchronous calls to non-scaling backends inevitably lead to connection starvation and elevated error rates during peak traffic. Introducing asynchronous messaging breaks the temporal coupling between the client request and the third-party execution, fulfilling both customer responsiveness and backend protection.
Adaptive Throttling is a client-side resiliency technique where the calling service dynamically tracks the proportion of backend request failures or high latencies. When the failure rate exceeds a specified threshold, the client proactively drops a probability-calculated portion of outgoing requests locally to allow the dependency time to recover.
The application were handling non-essential background telemetry or optional enrichment calls where shedding load and losing requests during an emergency is preferable to taking down the platform.
While adaptive throttling is recommended to prevent non-scaling database and service meltdowns in synchronous architectures, it must be paired with message buffering (like Pub/Sub) when business requirements dictate zero data loss for transactional writes.
Apigee Response Caching is a feature that stores responses from target backend servers in memory or persistent cache to serve subsequent, identical read requests directly from the API gateway without contacting the backend server.
The workload consisted of high-volume read queries for static product details or catalog pricing where serving identical cached data across users is acceptable.
While caching is a standard recommendation to mitigate slow backends for read-intensive APIs, transactional processing workflows require asynchronous decoupling patterns rather than gateway-level response caching.
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