Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A development team is building a microservices application using supported IDEs (such as IntelliJ IDEA and VS Code) that consists of a Cloud Run frontend and backend services deployed to Google Kubernetes Engine (GKE). The team wants to streamline their development and operations workflow to meet the following requirements:
Dockerfiles, and locally debug the Cloud Run service with rapid iterative feedback.CrashLoopBackOff and high-latency issues in deployed GKE workloads by correlating logs, metrics, and configurations to identify probable root causes, while receiving AI-driven recommendations for Pod Disruption Budgets and autoscaling.Which approach should the team adopt?
skaffold.yaml modules in watch mode for GKE, combined with Gemini Cloud Assist (including Investigations) in the Google Cloud console for root-cause analysis and GKE workload optimization.Cloud Code is an IDE extension for environments such as IntelliJ IDEA, VS Code, and Cloud Shell Editor that brings Google Cloud services directly into the developer workflow. Gemini Cloud Assist is an AI-powered collaborator in the Google Cloud console designed to streamline cloud design, troubleshooting, and workload optimization across services like GKE and Cloud Run.
skaffold.yaml modules and running both Kubernetes and emulated Cloud Run sessions in watch mode, automatically reapplying changes for a fast inner-loop feedback cycle.Dockerfile maintenance.skaffold.yaml dependencies.This combination pairs IDE-native container emulation and automated Kubernetes deployment (Cloud Code) with platform-aware operational intelligence (Gemini Cloud Assist), addressing both local developer velocity and production cluster troubleshooting without introducing unnecessary manual scripts or unrelated tools.
gcloud builds submit scripts to redeploy to GKE on every code change, and use Gemini Cloud Assist in FinOps Hub and the Google Cloud mobile app to diagnose CrashLoopBackOff errors and configure Pod Disruption Budgets.Cloud Workstations provides managed, containerized IDE environments hosted inside a Virtual Private Cloud (VPC) for standardized, secure enterprise development. FinOps Hub focuses on cloud financial management—analyzing spend, trends, waste, and resource utilization—while the Google Cloud mobile app acts as an on-the-go companion for service monitoring and basic incident triage.
gcloud builds submit to rebuild and redeploy to a remote GKE cluster on every code edit introduces significant latency compared to Cloud Code's local Cloud Run emulator and skaffold.yaml watch mode.CrashLoopBackOff stack traces or application latency.skaffold.yaml watch-mode workflows.gcloud) scripts are great for CI/CD automation, not rapid local iterative debugging.This approach would be appropriate if the primary goals were enforcing VPC-bound developer workstations, automating remote CI/CD builds, tracking billing waste in FinOps Hub, and triaging alerts while away from a computer.
Even when using Cloud Workstations, developers still pair the environment with Cloud Code and web-console Gemini Cloud Assist tools to achieve fast inner-loop container emulation and deep GKE root-cause analysis.
Dockerfiles and kubectl scripts, test the Cloud Run service locally using the Apigee Emulator, and paste cluster logs into Gemini Code Assist chat in the IDE to inspect live GKE metrics and Pod Disruption Budgets.The Apigee Emulator is a local runtime integrated into Cloud Code specifically for developing and testing Apigee API proxies. Gemini Code Assist is an AI coding assistant embedded in IDEs (including Cloud Shell Editor, VS Code, and JetBrains IDEs) that helps developers write, refactor, document, and unit-test source code using local workspace context.
PORT-based HTTP/gRPC workloads.Dockerfiles contradicts the requirement to build container images from source code without maintaining Dockerfiles, which Google Cloud buildpacks handle automatically.CrashLoopBackOff and cluster-wide latency requires correlating live cloud logs, metrics, and Kubernetes resource configurations via Gemini Cloud Assist Investigations.This approach would fit a scenario focused on building and unit-testing Apigee API proxies locally while refactoring application source code inside Cloud Shell Editor.
A common misconception is treating Gemini Code Assist and Gemini Cloud Assist as interchangeable. Gemini Code Assist focuses on IDE-level software development, whereas Gemini Cloud Assist specializes in cloud infrastructure operations, cost/reliability optimization, and live incident investigations.
.aiexclude file and @REPOSITORY_NAME remote repository context to inspect live GKE runtime metrics, and use Gemini assistance in Artifact Analysis to resolve CrashLoopBackOff latency.Cloud Code's Compute Engine integration allows developers to browse VMs, open terminal sessions, and transfer files from an IDE. In Gemini Code Assist, an .aiexclude file prevents sensitive local files (like API keys) from being used as AI context, while @REPOSITORY_NAME scopes chat prompts to indexed remote source repositories. Artifact Analysis with Gemini assistance helps users ask questions about container image vulnerabilities.
skaffold.yaml deployments to GKE..aiexclude nor @REPOSITORY_NAME connects the IDE to live GKE cluster metrics, Pod logs, or autoscaling policies; they only filter or focus static source-code repositories.CrashLoopBackOff and high-latency issues require analyzing live container logs, runtime metrics, and Kubernetes configurations..aiexclude acts similarly to .gitignore (without ! negation) to block sensitive workspace files from Gemini Code Assist context.@REPOSITORY_NAME requires code customization indexing and retrieves organizational code patterns, not production observability telemetry.This combination would fit a task involving managing Compute Engine VMs from an IDE, protecting sensitive local secrets from AI context, querying private Git repository conventions, and auditing container CVEs in Artifact Analysis.
Effective cloud-native troubleshooting requires matching observability signals to the right AI workflow: Artifact Analysis handles build-time image security, while Gemini Cloud Assist Investigations handles runtime logs, metrics, and cluster configuration anomalies.
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