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.
A DevOps engineer is reviewing Active Assist recommendations across an enterprise Google Cloud environment to optimize operational costs and resource utilization. The recommender hub has generated multiple insights across compute, networking, and disaster recovery architectures:
highmem instance type.Which recommendation represents the highest business impact and technical feasibility for immediate FinOps cost reduction while minimizing operational risk?
This option proposes forcing all cross-VPC and outbound traffic through centralized Next-Generation Firewall (NGFW) virtual appliances hosted within a centralized hub network using internal passthrough Network Load Balancers.
The organization had an explicit compliance requirement mandating centralized third-party vendor L7 deep packet inspection for every workload packet.
Active Assist VM rightsizing recommendations identify instances where compute allocations do not match actual runtime metrics, allowing organizations to reduce virtual CPU (vCPU) allocation while retaining sufficient memory for cache-dependent workloads.
highmem shape (offering ~8 GB RAM per vCPU) eliminates waste from unutilized vCPUs while protecting database performance.gcloud), or standard maintenance windows.Compared to complex network topology shifts (Item 2 and Item 3) or compromising disaster recovery readiness (Item 4), rightsizing compute resources based on working set analysis delivers immediate ROI with minimal operational friction.
This option involves deleting pre-deployed, stopped Compute Engine virtual machines and their attached Persistent Disks in a secondary disaster recovery (DR) region.
The workload's disaster recovery tier transitioned to an ultra-high RTO policy where cold-start infrastructure-as-code recreation via Terraform from off-site object storage backups was formally approved.
This option involves co-locating Kafka Connect distributed workers into a single target region alongside the managed Kafka cluster without considering the geographic distribution of external data sinks and sources.
All Kafka topics, connector dependencies, source databases, and analytics sink endpoints resided exclusively within the same target region, ensuring zero cross-region traffic.
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