Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
Your team is deploying an event-driven data pipeline in Google Cloud. An Eventarc trigger is configured to listen for state changes in Dataflow jobs and route those events to an internal, authenticated Cloud Run service for automated post-processing.
After creating the trigger, you notice that the Cloud Run service is never triggered, and the trigger logs display the following error message:
The request was not authenticated. Either allow unauthenticated invocations or set the proper Authorization header.
Which Identity and Access Management (IAM) configuration should you implement to resolve this issue securely?
The Eventarc Admin (roles/eventarc.admin) role grants complete control over Eventarc resources, allowing users to create, list, modify, and delete triggers, channels, and enrollments across a project.
roles/eventarc.admin manages trigger infrastructure, but does not provide HTTP invocation rights (run.routes.invoke) to execute private Cloud Run containers.A platform administrator needed full rights to manage, update, or delete Eventarc triggers and configurations within a Google Cloud project.
The Pub/Sub Publisher (roles/pubsub.publisher) role allows an identity or service agent to publish messages to Google Cloud Pub/Sub topics.
run.googleapis.com), which requires invocation rights, not messaging write rights.pubsub.topics.publish to send payloads to topics.You were configuring an Eventarc trigger for direct events from Cloud Storage and needed to authorize the Cloud Storage service agent (service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com) to publish notification events to the underlying Pub/Sub topic.
The Cloud Run Admin (roles/run.admin) role is an administrative IAM role that grants full management access over Cloud Run resources. This includes creating, modifying, deleting, and reconfiguring services and revisions across the resource hierarchy.
--service-account), not the default Compute Engine service account.roles/run.admin) at the project level provides excessive privileges, including resource deletion and configuration changes, rather than simple execution rights.A pipeline engineer or CI/CD service account needed comprehensive permissions to build, deploy, update configurations, and delete Cloud Run services across a development project.
The Cloud Run Invoker (roles/run.invoker) role is a predefined Identity and Access Management (IAM) role in Google Cloud. It provides the specific run.routes.invoke and run.services.invoke permissions required to send HTTP requests to private, authenticated Cloud Run services and jobs.
roles/run.invoker allows this identity to authenticate against the target service.roles/run.invoker directly on the specific Cloud Run service—rather than across the entire project—restricts invocation rights strictly to the target container without granting administrative control.Cloud Run services are deployed private by default. When routing events from services such as Dataflow or Cloud Storage to authenticated Cloud Run targets via Eventarc, binding roles/run.invoker to the trigger's designated service account is the Google-recommended approach for secure, reliable event delivery.
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