Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise DevOps team is configuring automated data migration from Microsoft Azure Blob Storage into Cloud Storage buckets. The organization's security policy enforces strict governance rules across all cloud environments:
Which strategy should the team implement to fulfill these requirements for Storage Transfer Service?
Workload Identity Federation enables Google Cloud services and external workloads to securely exchange identity credentials without managing or storing static, long-lived API keys, client secrets, or private key JSON files. For Storage Transfer Service, Google Cloud uses its managed service agent identity to generate short-lived OpenID Connect (OIDC) ID tokens that external identity providers (such as Microsoft Entra ID / Azure AD) validate natively.
roles/iam.serviceAccountTokenCreator) role to the managed Storage Transfer Service service agent (service-PROJECT_NUMBER@gcp-sa-storagetransfer.iam.gserviceaccount.com) allows it to create ephemeral OIDC ID tokens on demand.Federating the native Google Cloud service agent with Azure App Registration creates a completely keyless architecture. It satisfies the strict prohibition against static secrets while ensuring minimal administrative maintenance.
GKE Workload Identity allows workloads deployed inside Google Kubernetes Engine (GKE) clusters to impersonate Google Cloud IAM service accounts by linking a Kubernetes Service Account (KSA) to a Google Service Account (GSA). This removes the need to store service account private key JSON files inside Kubernetes secrets.
iam.gke.io/gcp-service-account and workload identity pools.The workload was a custom containerized microservice deployed on GKE that needed to interact with Google Cloud APIs without local service account key files.
While GKE Workload Identity is an essential pattern for Kubernetes workloads, native cross-cloud services like Storage Transfer Service utilize built-in multi-cloud Workload Identity Federation directly through service agents.
Google Cloud allows storing third-party credentials—such as an Azure Storage Shared Access Signature (SAS) token or storage account access key—inside Secret Manager. The Storage Transfer Service REST API can consume the secret reference via the credentialsSecret field in transferSpec.azureBlobStorageDataSource to authenticate against Azure Storage.
transferSpec.azureBlobStorageDataSource.credentialsSecret REST API field.The organization permitted managed secret storage for third-party cloud keys and target external systems lacked support for OIDC-based Workload Identity Federation.
Secret Manager is an enterprise best practice for managing unavoidable secrets, but native identity federation should always supersede stored secrets when supported by both platforms.
Active Directory Federation Services (AD FS) is an on-premises or VM-hosted identity solution that provides single sign-on and claims-based authentication across enterprise applications using protocols such as SAML, WS-Federation, and Integrated Windows Authentication (IWA).
The requirement was to provide federated single sign-on for legacy enterprise users accessing on-premises Windows domain resources via hybrid IWA authentication.
Workload Identity Federation for modern cloud services uses direct OIDC trust relationships and does not depend on enterprise AD FS farms.
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