Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are building an event-driven customer onboarding application on Google Cloud. Your backend is an authenticated Cloud Run service in us-central1 that must receive events in the CloudEvents format from three sources:
us-central1You need to minimize delivery latency for Google Cloud events, adhere to least-privilege security, and avoid unnecessary operational overhead.
How should you configure event routing for this architecture?
google.cloud.audit.log.v1.written) for Cloud Storage object creation, a Cloud Pub/Sub trigger for the custom microservice, and a Third-party trigger for the SaaS provider.Cloud Audit Logs triggers (google.cloud.audit.log.v1.written) capture Admin Activity and Data Access log entries generated by Google Cloud services and route matching entries to a target destination. A global Eventarc trigger aggregates events across all regions rather than binding to a specific regional endpoint.
us-central1 Cloud Storage bucket and us-central1 Cloud Run service introduces unnecessary performance overhead and potential data residency violations.serviceName and methodName fields and do not provide the strongly typed resource-level schemas offered by direct events.The Google Cloud source service only emitted Cloud Audit Logs (with no direct event support), events genuinely originated across all regions globally, and strict least-privilege IAM restrictions were not required for the trigger identity.
us-central1 associated with a user-managed service account granted roles/run.invoker: use a Google sources trigger for the direct Cloud Storage event (google.cloud.storage.object.v1.finalized), a Cloud Pub/Sub trigger (google.cloud.pubsub.topic.v1.messagePublished) for the custom microservice, and a Third-party trigger for the SaaS provider.Eventarc Standard is a fully managed eventing service that asynchronously routes state changes from Google Cloud providers, custom applications, and third-party SaaS sources to serverless destinations. Regardless of the originating source, Eventarc delivers every event as an HTTP request formatted according to the CloudEvents specification in binary content mode.
google.cloud.storage.object.v1.finalized) delivers Cloud Storage notifications in seconds using strongly typed schemas, avoiding the higher latency and extra cost of Cloud Audit Logs.google.cloud.pubsub.topic.v1.messagePublished) lets your custom microservice emit events through a scalable message bus, while a Third-party trigger integrates eligible SaaS providers—all normalized into CloudEvents.us-central1 matches both the Cloud Storage bucket and the Cloud Run service, preventing cross-region latency and data residency issues.roles/run.invoker ensures authenticated invocation of the Cloud Run receiver.Creating dedicated, regionally aligned Eventarc triggers per event type leverages direct Google events where available, supports custom and SaaS producers seamlessly, enforces least-privilege IAM, and guarantees uniform CloudEvents delivery with minimal operational effort.
roles/run.invoker targeting the Cloud Run service.A direct Pub/Sub push subscription delivers messages published to a Cloud Pub/Sub topic directly to an HTTPS endpoint, such as a Cloud Run service, as POST requests. While it can authenticate calls to Cloud Run using a service account with roles/run.invoker, it operates strictly as a raw Pub/Sub transport mechanism.
message object without CloudEvents headers (ce-type, ce-source, ce-id).Your application only needed to consume messages from a single Pub/Sub producer, already used native Pub/Sub message parsing, and did not require the CloudEvents standard or managed third-party SaaS integrations.
us-central1 with --event-data-content-type=application/protobuf, use wildcards in --event-filters to match events from Cloud Storage, the custom microservice's Pub/Sub topic, and the SaaS provider, and assign a user-managed service account with roles/run.viewer.Eventarc triggers use --event-filters to declare exact match criteria for routing events from a specific source to a target destination. Additionally, Eventarc allows configuring --event-data-content-type as application/json or application/protobuf for certain supported Google Cloud event providers to reduce payload size.
--event-filters performs exact matching and does not support wildcards or regular expressions. Furthermore, each trigger accepts only one immutable type filter (EVENT_FILTER_TYPE), so a single trigger cannot match Cloud Storage, Pub/Sub, and third-party provider events simultaneously.application/protobuf encoding is not supported for custom sources, third-party providers, or direct events from Pub/Sub.roles/run.viewer only allows viewing Cloud Run service metadata; it does not permit invoking an authenticated Cloud Run service, which specifically requires roles/run.invoker. Events delivered with roles/run.viewer will fail with HTTP 403 Forbidden errors.--event-filters-path-pattern, not for event types or general filters.EVENT_FILTER_TYPE cannot be modified.application/json.Each event source had its own trigger, application/protobuf were only applied to supported Google direct events (like Cloud Storage), and the service account held roles/run.invoker instead of roles/run.viewer.
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 Validated