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 modernizing its event ingestion architecture on Google Cloud to support rapid feature rollout for downstream analytics teams. The infrastructure team has limited operational bandwidth and wants to avoid accumulating operational technical debt, such as manual capacity planning, broker maintenance, partition rebalancing, and custom cross-region data replication.
However, some developers argue for deploying and managing open-source messaging software on Compute Engine to maintain multi-cloud API portability.
Which architectural trade-off recommendation best balances organizational agility and technical debt reduction with the enterprise's operational needs?
Deploy self-managed Apache Kafka clusters on Compute Engine across multiple zones to prioritize multi-cloud API portability, while establishing automated scripts for broker provisioning and partition rebalancing.
Use Google Cloud Managed Service for Apache Kafka because it completely eliminates cluster sizing, partition planning, and replica configuration while ensuring cross-cloud portability.
Adopt Cloud Pub/Sub to prioritize operational simplicity and rapid deployment, accepting proprietary API coupling in exchange for fully managed dynamic scaling, zero partition management, and automated global data distribution.
Develop a custom messaging service using Cloud Run and Memorystore to retain full control over data structures and avoid vendor-specific messaging protocols.
Deploy self-managed Apache Kafka clusters on Compute Engine across multiple zones to prioritize multi-cloud API portability, while establishing automated scripts for broker provisioning and partition rebalancing.
Use Google Cloud Managed Service for Apache Kafka because it completely eliminates cluster sizing, partition planning, and replica configuration while ensuring cross-cloud portability.
Adopt Cloud Pub/Sub to prioritize operational simplicity and rapid deployment, accepting proprietary API coupling in exchange for fully managed dynamic scaling, zero partition management, and automated global data distribution.
Cloud Pub/Sub is a wholly managed, serverless, and globally distributed messaging service provided natively by Google Cloud. It provides asynchronous many-to-many messaging that decouples services producing events from those processing them.
The core trade-off when selecting messaging systems is between operational simplicity and portability. For teams with constrained operations seeking maximum agility and low maintenance overhead, trading third-party multi-cloud API portability for a fully managed, serverless model yields the highest long-term velocity and lowest operational technical debt.
Develop a custom messaging service using Cloud Run and Memorystore to retain full control over data structures and avoid vendor-specific messaging protocols.
StudyCerts
StudyCerts