Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company deploys a web application across multiple zones using a Compute Engine regional Managed Instance Group (MIG). The application instances require approximately three minutes to complete their startup scripts and initialize dependencies before they can successfully answer HTTP requests. After attaching an autohealing policy with an application health check, newly created instances are repeatedly marked unhealthy and recreated before they finish initializing.
Which configuration adjustment should you make to the autohealing policy to resolve this issue?
Google Cloud health checking services rely on specific Google IP address ranges (130.211.0.0/22 and 35.191.0.0/16) to probe VM instances and determine their application availability.
TIMEOUT or UNHEALTHY.You needed to simulate a total health check probe failure across a test instance group to verify alerting rules when probes cannot reach backends.
An unmanaged instance group (UMIG) is a collection of individual, heterogeneous Compute Engine virtual machines that do not share a common instance template and do not support automated management.
You had to group existing, pre-configured virtual machines of different machine types and configurations that do not share an instance template or automated management requirements.
The initial delay (initialDelaySec) is a core configuration setting within a Managed Instance Group (MIG) autohealing policy. It defines the period of time (in seconds) that the autohealer must wait before evaluating failed health check signals on a newly launched virtual machine (VM).

0 and 3600 seconds (up to 1 hour) to accommodate diverse application boot profiles.Configuring initialDelaySec directly addresses the root cause of the problem without disabling health checks, altering network firewall security, or reducing the high-availability benefits of running a regional MIG.
The unhealthy threshold specifies the number of consecutive failed probe responses required before Compute Engine marks an instance as UNHEALTHY.
The application initialized instantly and required ultra-rapid failover detection where even a single dropped packet should trigger immediate mitigation.
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