Eventarc for event routing in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Eventarc trigger that listens to Cloud Storage events.

GCP

gcloud eventarc triggers create my-trigger --destination-run-service=my-service --destination-run-region=us-central1 --event-filters=type=[1]

Drag options to blanks, or click blank then click option'

Agoogle.cloud.scheduler.job.v1.executed

Bgoogle.cloud.storage.object.v1.finalized

Cgoogle.cloud.pubsub.topic.v1.messagePublished

Dgoogle.cloud.firestore.document.v1.written

Attempts:

3 left

💡 Hint

Common Mistakes

Using Pub/Sub or Firestore event types instead of Cloud Storage event types.

Confusing event type names with service names.

The event type google.cloud.storage.object.v1.finalized corresponds to Cloud Storage object creation events, which Eventarc can listen to.

2fill in blank

medium

Complete the command to specify the region where the Eventarc trigger will be created.

GCP

gcloud eventarc triggers create my-trigger --destination-run-service=my-service --destination-run-region=[1] --event-filters=type=google.cloud.storage.object.v1.finalized

Drag options to blanks, or click blank then click option'

Aeurope-west1

Basia-east1

Cus-central1

Dsouthamerica-east1

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a region where Cloud Run or Eventarc is not supported.

Using a region that does not match the Cloud Run service location.

The region us-central1 is a common and supported region for Eventarc triggers and Cloud Run services.

3fill in blank

hard

Fix the error in the Eventarc trigger creation command by selecting the correct flag for the destination service.

GCP

gcloud eventarc triggers create my-trigger --destination-run-service=[1] --destination-run-region=us-central1 --event-filters=type=google.cloud.storage.object.v1.finalized

Drag options to blanks, or click blank then click option'

Amy-service

Bmy-service-run

Cmy-service-cloudrun

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong flag name for the destination service.

Adding extra suffixes to the service name.

The correct flag to specify the Cloud Run service is --destination-run-service, not --destination-service. The value should be the service name, here my-service.

4fill in blank

hard

Fill both blanks to create an Eventarc trigger that listens to Pub/Sub topic messages and routes them to a Cloud Run service.

GCP

gcloud eventarc triggers create pubsub-trigger --destination-run-service=[1] --destination-run-region=[2] --event-filters=type=[3] --event-filters=source=//pubsub.googleapis.com/projects/my-project/topics/my-topic

Drag options to blanks, or click blank then click option'

Amy-pubsub-service

Bus-east1

Cgoogle.cloud.pubsub.topic.v1.messagePublished

Deurope-west1

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing event types for different services.

Using incorrect region or service names.

The trigger routes Pub/Sub messages (google.cloud.pubsub.topic.v1.messagePublished) to the Cloud Run service my-pubsub-service in the us-east1 region.

5fill in blank

hard

Fill all three blanks to define an Eventarc trigger in YAML that routes Firestore document changes to a Cloud Run service.

GCP

apiVersion: eventarc.googleapis.com/v1
kind: Trigger
metadata:
  name: firestore-trigger
spec:
  destination:
    cloudRunService: [1]
    region: [2]
  eventFilters:
  - attribute: type
    value: [3]

Drag options to blanks, or click blank then click option'

Afirestore-service

Bus-west1

Cgoogle.cloud.firestore.document.v1.written

Dus-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong event filter values.

Mixing up region names.

Incorrect service names.

The YAML defines a trigger named firestore-trigger that listens to Firestore document write events (google.cloud.firestore.document.v1.written) and routes them to the Cloud Run service firestore-service in the us-west1 region.