Eventarc for event routing in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Eventarc route events in Google Cloud?

Which statement best describes how Eventarc routes events to targets?

A Eventarc stores all events in a database before sending them to targets in batches every hour.

B Eventarc listens for events from sources and forwards them to specified Cloud Run services or other targets based on filters.

C Eventarc requires manual polling of event sources to retrieve events and then pushes them to targets.

D Eventarc only routes events between Compute Engine instances using internal IP addresses.

💡 Hint

Think about how Eventarc connects event sources to services automatically.

Eventarc automatically listens for events from supported sources and routes them to targets like Cloud Run services based on event filters. It does not batch or require manual polling.

❓ Architecture

intermediate

Eventarc architecture for multi-region event delivery

You want to design an Eventarc setup that delivers events from multiple regions to a single Cloud Run service in us-central1. Which architecture ensures low latency and reliability?

A Create Eventarc triggers in each source region forwarding events directly to the Cloud Run service in us-central1.

B Use a single Eventarc trigger in us-central1 that pulls events from all regions using a global event bus.

C Deploy Cloud Run services in each region and use Eventarc triggers to route events locally, then forward results to us-central1 manually.

D Configure Eventarc to replicate events to Pub/Sub topics in us-central1, then trigger Cloud Run from those topics.

💡 Hint

Consider how Eventarc triggers work regionally and how direct routing affects latency.

Eventarc triggers are regional and listen to events in their region. Creating triggers in each source region that forward events directly to the Cloud Run service in us-central1 reduces latency and avoids extra hops.

❓ security

advanced

Securing Eventarc triggers with least privilege

You want to ensure Eventarc triggers have the minimum permissions needed to deliver events to a Cloud Run service. Which IAM role should you assign to the Eventarc service account?

A roles/eventarc.admin on the Cloud Run service

B roles/owner on the Cloud Run service

C roles/editor on the entire project

D roles/run.invoker on the Cloud Run service

💡 Hint

Think about the permission needed to invoke a Cloud Run service securely.

The Eventarc service account needs the roles/run.invoker role on the Cloud Run service to invoke it. Assigning broader roles like editor or owner violates least privilege principles.

❓ service_behavior

advanced

Eventarc trigger filter behavior

Given an Eventarc trigger with the filter type=google.cloud.storage.object.v1.finalized, what happens when a new object is created in a Cloud Storage bucket?

A The trigger activates and routes the event to its target because the event type matches the filter.

B The trigger ignores the event because it only listens for deletion events.

C The trigger activates but fails to route the event because the filter syntax is incorrect.

D The trigger routes all events from Cloud Storage regardless of type.

💡 Hint

Consider what the event type finalized means in Cloud Storage.

The filter matches events when a new object is finalized (created or overwritten) in Cloud Storage. Thus, the trigger activates and routes the event to its target.

✅ Best Practice

expert

Optimizing Eventarc for high event volume

You expect a very high volume of events from multiple sources routed to a Cloud Run service via Eventarc. Which approach best optimizes performance and cost?

A Disable Eventarc and poll event sources manually to control event flow.

B Use a single Eventarc trigger with broad filters sending all events to one Cloud Run service instance.

C Use multiple Eventarc triggers with specific filters to route subsets of events to separate Cloud Run services for parallel processing.

D Route all events to a single Pub/Sub topic and have Cloud Run subscribe directly without Eventarc.

💡 Hint

Think about splitting workload to avoid bottlenecks and reduce costs.

Using multiple triggers with specific filters allows parallel processing and better scaling. A single broad trigger can cause bottlenecks and higher costs. Polling manually or bypassing Eventarc loses managed routing benefits.