- A
Store a service account JSON key as a GitHub Actions secret and use it in the workflow
Why wrong: JSON key files are long-lived credentials and a security risk — they can be leaked via logs, forks, or misconfigurations. Workload Identity Federation eliminates the need for key files.
- B
Workload Identity Federation with GitHub Actions as the identity provider
Workload Identity Federation allows GitHub Actions workflows to authenticate to GCP using the workflow's OIDC token — no service account key file is ever created or stored.
- C
OAuth 2.0 user credentials from a developer's Google account
Why wrong: User credentials tie access to a specific person's account — not appropriate for automated CI/CD pipelines.
- D
API keys created for the Artifact Registry service
Why wrong: Artifact Registry uses IAM for access control — API keys are not a supported authentication mechanism for Artifact Registry.
Quick Answer
The correct answer is Workload Identity Federation with GitHub Actions as the identity provider. This mechanism allows a GitHub Actions workflow to exchange a GitHub-issued OIDC token for a temporary GCP access token, enabling authentication to Artifact Registry without ever storing a long-lived service account key file. On the Google Associate Cloud Engineer exam, this scenario tests your understanding of secure, keyless authentication for external CI/CD pipelines—a common trap is choosing a service account key stored in GitHub Secrets, which violates the “no long-lived keys” requirement. Remember that Workload Identity Federation eliminates static credentials by trusting an external identity provider’s token directly. A helpful memory tip: “OIDC exchange, no keys to arrange.”
Google ACE Configuring access and security Practice Question
This ACE practice question tests your understanding of configuring access and security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A CI/CD pipeline running outside GCP (on GitHub Actions) needs to authenticate to GCP to push images to Artifact Registry, without storing any long-lived service account key files. Which authentication mechanism achieves this?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Workload Identity Federation with GitHub Actions as the identity provider
Workload Identity Federation allows a GitHub Actions workflow to exchange a GitHub-issued OIDC token for a GCP access token, enabling authentication to Artifact Registry without storing any long-lived service account keys. This is the recommended approach for non-GCP CI/CD systems because it eliminates the security risk of managing static credentials while still granting fine-grained, short-lived access to GCP resources.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store a service account JSON key as a GitHub Actions secret and use it in the workflow
Why it's wrong here
JSON key files are long-lived credentials and a security risk — they can be leaked via logs, forks, or misconfigurations. Workload Identity Federation eliminates the need for key files.
- ✓
Workload Identity Federation with GitHub Actions as the identity provider
Why this is correct
Workload Identity Federation allows GitHub Actions workflows to authenticate to GCP using the workflow's OIDC token — no service account key file is ever created or stored.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
OAuth 2.0 user credentials from a developer's Google account
Why it's wrong here
User credentials tie access to a specific person's account — not appropriate for automated CI/CD pipelines.
- ✗
API keys created for the Artifact Registry service
Why it's wrong here
Artifact Registry uses IAM for access control — API keys are not a supported authentication mechanism for Artifact Registry.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often default to storing a service account key as a secret (Option A) because it's a familiar pattern, failing to recognize that Workload Identity Federation is the modern, keyless alternative specifically designed for external CI/CD providers like GitHub Actions.
Detailed technical explanation
How to think about this question
Workload Identity Federation uses the OIDC (OpenID Connect) protocol: GitHub Actions generates a JWT signed by GitHub's OIDC provider, which GCP's IAM validates against a workload identity pool. The pool maps the GitHub repository and branch to a GCP service account, issuing a short-lived access token (typically 1 hour) that the pipeline uses to authenticate `gcloud auth configure-docker` or direct API calls. A subtle behavior is that the OIDC token's `sub` claim includes the GitHub repository and environment (e.g., `repo:my-org/my-repo:ref:refs/heads/main`), allowing precise branch-level access control.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Configuring access and security — study guide chapter
Learn the concepts, then practise the questions
- →
Configuring access and security practice questions
Targeted practice on this topic area only
- →
All ACE questions
500 questions across all exam domains
- →
Google Associate Cloud Engineer study guide
Full concept coverage aligned to exam objectives
- →
ACE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Setting up a cloud solution environment practice questions
Practise ACE questions linked to Setting up a cloud solution environment.
Planning and configuring a cloud solution practice questions
Practise ACE questions linked to Planning and configuring a cloud solution.
Deploying and implementing a cloud solution practice questions
Practise ACE questions linked to Deploying and implementing a cloud solution.
Ensuring successful operation of a cloud solution practice questions
Practise ACE questions linked to Ensuring successful operation of a cloud solution.
Configuring access and security practice questions
Practise ACE questions linked to Configuring access and security.
ACE fundamentals practice questions
Practise ACE questions linked to ACE fundamentals.
ACE scenario practice questions
Practise ACE questions linked to ACE scenario.
ACE troubleshooting practice questions
Practise ACE questions linked to ACE troubleshooting.
Practice this exam
Start a free ACE practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this ACE question test?
Configuring access and security — This question tests Configuring access and security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Workload Identity Federation with GitHub Actions as the identity provider — Workload Identity Federation allows a GitHub Actions workflow to exchange a GitHub-issued OIDC token for a GCP access token, enabling authentication to Artifact Registry without storing any long-lived service account keys. This is the recommended approach for non-GCP CI/CD systems because it eliminates the security risk of managing static credentials while still granting fine-grained, short-lived access to GCP resources.
What should I do if I get this ACE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.