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 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?
Google Cloud Managed Service for Apache Kafka provides a managed environment for running Apache Kafka on Google Cloud, simplifying broker lifecycle management while supporting standard Apache Kafka client APIs.
The organization had existing Kafka workloads or applications written strictly against the Kafka API that needed to be migrated to Google Cloud with minimal code rewrites while maintaining a consistent multi-cloud development model.
Deploying self-managed Apache Kafka on Compute Engine involves provisioning virtual machine instances, deploying Kafka brokers and ZooKeeper/KRaft clusters, and manually configuring storage, networking, and cluster failover.
The organization had strict regulatory requirements to use identical open-source binaries across on-premises and multiple cloud environments and possessed a dedicated 24/7 operations team to maintain Kafka infrastructure.
This approach entails building a proprietary queuing or messaging system using Cloud Run containerized microservices backed by an in-memory datastore like Memorystore for Redis.
The application required ultra-low sub-millisecond in-memory ephemeral queueing with unique data mutations that standard pub/sub or streaming engines cannot support.
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.

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