nerdexam
Google

PROFESSIONAL-CLOUD-SECURITY-ENGINEER · Question #271

Your organization has a centralized identity provider that is used to manage human and machine access. You want to leverage this existing identity management system to enable on-premises…

The correct answer is D. Enable Workload Identity Federation. Create a workload identity pool and specify the on-premises. Workload Identity Federation allows external workloads - including on-premises applications - to authenticate to Google Cloud by exchanging credentials from an existing identity provider (via OIDC, SAML 2.0, or AWS) for short-lived Google credentials. This eliminates the need…

Submitted by lucia.co· Apr 18, 2026Configuring access within a cloud solution environment

Question

Your organization has a centralized identity provider that is used to manage human and machine access. You want to leverage this existing identity management system to enable on-premises applications to access Google Cloud without hard coded credentials. What should you do?

Options

  • AEnable Secure Web Proxy. Create a proxy subnet for each region that Secure Web Proxy will be
  • BEnable Workforce Identity Federation. Create a workforce identity pool and specify the on-
  • CEnable Identity-Aware Proxy (IAP). Configure IAP by specifying the groups and service accounts
  • DEnable Workload Identity Federation. Create a workload identity pool and specify the on-premises

How the community answered

(31 responses)
  • A
    3% (1)
  • B
    10% (3)
  • C
    16% (5)
  • D
    71% (22)

Explanation

Workload Identity Federation allows external workloads - including on-premises applications - to authenticate to Google Cloud by exchanging credentials from an existing identity provider (via OIDC, SAML 2.0, or AWS) for short-lived Google credentials. This eliminates the need for hardcoded service account keys. Workforce Identity Federation (option B) serves the same general purpose but is designed for human users (employees), not machine-to-machine workloads. IAP (option C) is for controlling human access to applications, not for enabling application-to-API authentication. Secure Web Proxy (option A) is a network egress control mechanism, unrelated to identity federation.

Topics

#Workload Identity Federation#Identity and Access Management (IAM)#Hybrid Cloud Access#Credential-less Access

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-SECURITY-ENGINEER Practice