Question 175 of 500

Quick Answer

The answer is to configure Workload Identity Federation between the on-premises identity provider and Google Cloud. This solution is correct because it allows on-premises applications to exchange tokens from an external IdP for short-lived Google Cloud access tokens, directly addressing the requirement for short-lived credentials without storing a service account key file. By federating trust, the on-premises workload never handles a static key, eliminating the primary security risk of long-lived secrets. On the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of identity federation as a secure alternative to downloading and managing service account keys, a common trap where candidates might incorrectly suggest using a service account key stored in a secret manager. The key memory tip is “federate, don’t store”—if the question mentions on-premises apps needing short-lived credentials and no key file, your answer is always Workload Identity Federation.

PCSE Practice Question: Configuring access within a cloud solution environment

This PCSE practice question tests your understanding of configuring access within a cloud solution environment. 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 company wants to allow its on-premises applications to access Google Cloud resources using short-lived credentials without storing a service account key file. Which solution should they use?

Question 1mediummultiple choice
Full question →

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

Configure Workload Identity Federation between the on-premises identity provider and Google Cloud.

Workload Identity Federation allows on-premises applications to exchange tokens from an external identity provider (IdP) for short-lived Google Cloud access tokens, eliminating the need to store a service account key file. This solution meets the requirement for short-lived credentials and avoids the security risk of long-lived static keys.

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.

  • Configure Workload Identity Federation between the on-premises identity provider and Google Cloud.

    Why this is correct

    This provides short-lived credentials without keys.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Set up a Cloud VPN connection and use private IPs to access resources.

    Why it's wrong here

    VPN provides network access, not authentication.

  • Create a service account and download a JSON key file to the on-premises server.

    Why it's wrong here

    Key files are long-lived credentials that should be avoided.

  • Use signed URLs to grant access for each request.

    Why it's wrong here

    Not suitable for programmatic access to APIs.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the distinction between network-level solutions (VPN) and identity-level solutions (federation), so candidates may incorrectly choose a VPN because it seems like a secure connection, but it does not solve the credential management requirement.

Detailed technical explanation

How to think about this question

Workload Identity Federation uses the Security Token Service (STS) to exchange a token from an external IdP (e.g., Azure AD, Okta, or ADFS) for a Google Cloud access token, following the OAuth 2.0 token exchange RFC 8693. The external token must include a subject (sub) claim that maps to a Google Cloud service account via attribute conditions, allowing fine-grained, short-lived access without managing key files.

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.

Related practice questions

Related PCSE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCSE 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 PCSE question test?

Configuring access within a cloud solution environment — This question tests Configuring access within a cloud solution environment — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Configure Workload Identity Federation between the on-premises identity provider and Google Cloud. — Workload Identity Federation allows on-premises applications to exchange tokens from an external identity provider (IdP) for short-lived Google Cloud access tokens, eliminating the need to store a service account key file. This solution meets the requirement for short-lived credentials and avoids the security risk of long-lived static keys.

What should I do if I get this PCSE 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

This PCSE 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 PCSE exam.