Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A media company is decomposing a legacy monolithic application into microservices on Google Cloud. When a user uploads a video to Cloud Storage, several downstream workflows must be triggered automatically. The engineering team has established the following architectural requirements:
How does a serverless event-driven architecture using services like Eventarc, Pub/Sub, and Cloud Run support these requirements?
Synchronous service-to-service communication is an architectural pattern where a calling service sends a direct request to a downstream service and blocks further execution until it receives a response. In a sequential chain of direct calls, each component must know the network location and API contract of the next service, waiting for each task to complete before moving forward.
This approach would be appropriate if the scenario required a strictly sequential, transactional request-response workflow where the client immediately needed the combined output of every step before proceeding, or if orchestrating a step-by-step state machine where each step explicitly depends on the output of the previous step.
Modern event-driven architectures on Google Cloud intentionally replace direct, blocking service-to-service calls with asynchronous event routing via Eventarc and Pub/Sub. In an asynchronous model, the event producer only needs to publish the event once, and the event router handles pushing the notification to all subscribed Cloud Run services independently.
Predictive autoscaling is a feature of Compute Engine managed instance groups (MIGs) that analyzes historical metrics—such as CPU utilization—to forecast future workload demand and automatically provision virtual machine (VM) instances ahead of anticipated traffic peaks. It combines real-time metrics with historical trends to scale infrastructure-as-a-service (IaaS) resources proactively.
This option would be the right choice if the organization were running a stateful or VM-based application on Compute Engine with recurring, predictable traffic spikes (such as daily business-hour surges) and needed to pre-provision VM capacity that takes several minutes to initialize.
Unlike Compute Engine autoscaling, which requires configuring metric thresholds and forecasting rules, serverless services like Cloud Run, Cloud Run functions, Pub/Sub, and Eventarc are inherently elastic. They respond instantly to incoming events without requiring capacity forecasting or VM provisioning.
A serverless event-driven architecture is a modern software design pattern in which decoupled microservices automatically react to state changes, known as events, without requiring developers to provision or manage underlying servers. In this model, event producers (such as Cloud Storage) generate immutable notifications when an action occurs, an event router or broker (such as Eventarc or Pub/Sub) ingests and filters those events, and event consumers (such as Cloud Run or Cloud Run functions) execute business logic in response.

Compared to tightly coupled or polling-based designs, combining managed event routers like Eventarc and Pub/Sub with serverless compute like Cloud Run maximizes agility and minimizes operational overhead. It allows engineering teams to focus entirely on building modular business capabilities and experimenting with new features rather than maintaining complex communication plumbing.
Continuous polling is a communication mechanism in which a client or consuming service repeatedly sends requests at regular intervals to a data source or remote service to check whether a state change has occurred. Even when no new data or events are available, the polling service must stay active and execute queries continuously.
This approach would be suitable if the application needed to retrieve data from a legacy external system or third-party endpoint that only supports pull-based queries and lacks the ability to emit events or push notifications.
Serverless event-driven architectures on Google Cloud use push-based messaging rather than continuous polling. When a file is uploaded to Cloud Storage, Eventarc or Pub/Sub automatically detects the state change and pushes the event to downstream Cloud Run services, enabling real-time processing while reducing network I/O and infrastructure costs.
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