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 architecting a multi-cloud continuous deployment pipeline using Argo CD hosted on an external Kubernetes cluster. The pipeline needs to deploy application artifacts and fetch sensitive database credentials directly from Google Cloud Secret Manager across projects.
Corporate security policy strictly prohibits the creation, distribution, and storage of downloadable long-lived service account keys (.json key files) within external CI/CD systems.
Which solution should the team implement to authenticate the external pipeline to Google Cloud while maintaining least-privilege access control?
This approach uses an automated serverless workflow to generate standard Google Cloud service account private keys on a schedule, injecting them as Kubernetes Secret objects into the external cluster for the CI/CD pipeline to mount.
roles/secretmanager.admin) role grants full administrative permissions over Secret Manager across the entire project (including secret deletion and IAM modifications), rather than restricting read access to specific secrets.Workload Identity Federation was not supported by the external identity provider and key rotation was the only available legacy mitigation.
This proposal attempts to store the external platform credentials in Secret Manager and access the Secret Manager REST API using basic HTTP username/password authentication.
A Google Cloud workload needed to connect outbound to an external third-party service (such as Azure Storage or an external database) using stored credentials retrieved from Secret Manager via standard IAM-authenticated API calls.
Workload Identity Federation allows workloads running outside of Google Cloud—such as on-premises environments, external Kubernetes clusters, AWS, or Azure—to impersonate Google Cloud IAM service accounts by exchanging external credentials (like OpenID Connect tokens) for short-lived Google Cloud access tokens, removing the need for long-lived service account keys.
roles/secretmanager.secretAccessor) role on the specific secret resources required by the deployment..json service account private keys.Workload Identity Federation provides a native, highly secure mechanism for federating identity across hybrid and multi-cloud environments. It satisfies corporate governance by preventing static secret exposure while strictly enforcing least-privilege IAM roles at the resource level.
Identity-Aware Proxy (IAP) TCP forwarding allows authorized users and administrative clients to establish encrypted tunnels over HTTPS to access administrative ports (such as SSH or RDP) on Compute Engine instances and internal resources without exposing public IP addresses.
roles/iap.tunnelResourceAccessor) role grants permission to connect through the tunnel, but does not provide credentials or permissions to interact with Google Cloud REST APIs.The DevOps team needed to establish secure administrative SSH/RDP connectivity to private VM instances hosting self-managed build agents without exposing them to the public internet.
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