Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Associate Cloud Engineer · Google Cloud
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users
C is the correct answer: • Re-creating VMs = Autohealing. Only Managed Instance Groups (MIGs) have the actual power to delete a frozen or broken VM and spin up a brand-new one to replace it. • Why not Load Balancers (A & B)? Load balancers only ignore broken VMs by routing traffic away from them. They cannot recreate them. • Why not Autoscaling (D)? Autoscaling adds extra VMs when your app gets busy. It does not monitor for or replace unresponsive VMs.
Option C is correct.