Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A software engineering team is developing a containerized microservices application targeted for Google Kubernetes Engine (GKE). The team uses the browser-based Cloud Shell Editor and wants to accelerate their development inner loop.
They have the following requirements:
Which workflow and configuration should the team implement in Cloud Shell Editor?
This option involves setting up an automated Continuous Integration and Continuous Delivery (CI/CD) pipeline utilizing Cloud Build, Artifact Registry, and Google Cloud Deploy to render Skaffold manifests, promote container releases across environments, and inspect runtime behavior via centralized logs.
The requirement was to automate the outer-loop release pipeline for merging code to shared staging and production GKE clusters with governance checks.
This option utilizes the Google Cloud SDK command gcloud builds submit to package and build images in Google Cloud infrastructure on every edit, while relying on Cloud Profiler and Cloud Trace for distributed performance analysis and latency profiling.
gcloud builds submit on every file save introduces substantial build latency and consumes unnecessary build minutes/quotas.gcloud builds submit builds container images remotely but does not manage Kubernetes rollout synchronization or debug port management.The objective was to analyze production microservice latency bottlenecks and memory consumption across distributed systems.
This option relies on running the command-line interface tool Skaffold (skaffold dev) in the Cloud Shell Terminal and manually managing kubectl port-forward commands to establish network tunnels to container debug ports, coupled with generic SSH attachment profiles.
skaffold dev manages continuous rebuilds and deployments, it does not automatically orchestrate IDE debugger attachment or rewrite runtime container entrypoints with debug flags the way skaffold debug within Cloud Code does.skaffold dev focuses primarily on the build-tag-deploy-watch cycle rather than interactive IDE debugging.A team was operating entirely in a headless terminal environment without an integrated development environment (IDE) or Cloud Code extension support.
Cloud Code in Cloud Shell Editor is an integrated extension that brings Google Cloud developer workflows directly into the browser-based IDE. Leveraging Skaffold (skaffold debug), Cloud Code provides a streamlined, continuous development workflow designed specifically for containerized workloads deployed to Google Kubernetes Engine (GKE), local minikube, or Cloud Run.
watch flag active in the cloudcode.kubernetes configuration, Cloud Code continuously detects local code modifications upon file save, automatically rebuilding container images via Google Cloud Build or local builders and redeploying manifests using kubectl.ptvsd, Delve for Go, or Java JDWP agent options), and creates network port forwarding rules from the GKE pod to the Cloud Shell environment.docker build, tag images, push to Artifact Registry, update deployment manifests, or manually execute kubectl port-forward.skaffold.yaml and editor launch behaviors via .vscode/launch.json.Using Cloud Code: Debug on Kubernetes provides full parity between the local development environment and cloud-hosted Kubernetes clusters while eliminating repetitive manual context switching, dramatically accelerating developer iteration cycles.
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