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.
Your enterprise operates a hybrid CI/CD pipeline where deployment runners in an on-premises data center deploy containerized workloads to on-premises Anthos/GKE Enterprise clusters. The on-premises environment connects to your Google Cloud Virtual Private Cloud (VPC) through Dedicated Cloud Interconnect.
You need to design a secure deployment workflow that satisfies the following requirements:
Which combination of architectural patterns and services should you implement?
This configuration routes outbound traffic through Cloud NAT to reach public Google APIs and stores long-lived service account keys inside HashiCorp Vault, reading secrets at deploy time to export them into container environment variables.
The workloads had no dedicated interconnect to Google Cloud and required egress-only translation to communicate over the public internet with a legacy application that only supports environment variable configuration.
This approach attempts to use Identity-Aware Proxy (IAP) TCP forwarding to proxy traffic to Artifact Registry and deploys standard, unencrypted Kubernetes Secrets into the Anthos cluster.
etcd.Administrators needed to establish temporary, context-aware administrative SSH sessions to specific bastion VMs in Google Cloud without exposing public IP addresses.
This approach sets up a Cloud Storage bucket to act as an intermediary cache for container artifacts and attempts to attach a Google Cloud IAM Service Account directly to on-premises virtualization infrastructure.
The workloads were running directly on native Compute Engine VMs within Google Cloud where the instance metadata server supplies Application Default Credentials automatically.
Private Google Access for on-premises hosts allows external networks connected via Cloud Interconnect or Cloud VPN to resolve and reach Google APIs and services—such as Artifact Registry and Secret Manager—using internal RFC 1918 or private VIP routing (private.googleapis.com or restricted.googleapis.com), completely avoiding internet transit. Workload Identity Federation allows non-Google Cloud compute workloads (such as on-premises CI/CD runners or Kubernetes pods) to use their native identity providers (such as OpenID Connect or SAML) to obtain short-lived Google Cloud credentials dynamically.
Combining Private Google Access over Cloud Interconnect with Workload Identity Federation adheres strictly to Google Cloud security architecture best practices for hybrid pipelines, mitigating risks of credential theft and data exfiltration while keeping all traffic on private channels.
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