Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A data engineering team manages a real-time analytics web application deployed on a Managed Instance Group (MIG) behind an external Application Load Balancer. During periods of heavy data ingestion, some virtual machines become temporarily busy and are slow to respond to requests.
The current configuration uses a single, aggressive health check for both the load balancer and the MIG's autohealing policy. As a result, the autohealer mistakes these busy instances for failed instances and prematurely recreates them, which reduces overall system availability and causes cascading failures.
What should you do to ensure the system gracefully handles temporary load spikes while still automatically recovering from true application failures?
In Google Cloud, Managed Instance Groups (MIGs) utilize health checks for two distinct purposes: load balancing and autohealing. While a load balancer uses health checks to determine where to route user traffic, an autohealing policy uses health checks to determine if a virtual machine (VM) is fundamentally broken and needs to be completely deleted and recreated.
Using a single, aggressive health check for both purposes is a common anti-pattern. An aggressive autohealer mistakes busy instances for failed instances and unnecessarily restarts them. Separating the health checks allows you to tune the load balancer for optimal user experience (fast failover) and tune the autohealer for optimal infrastructure stability (conservative recreation).
A TCP health check probes a virtual machine by attempting to establish a basic Transmission Control Protocol (TCP) connection on a specified port. It only verifies that the operating system's network stack is accepting connections on that port, without evaluating the actual application logic or HTTP response codes.
The application being deployed was a non-HTTP service (such as a custom binary protocol or database) where a TCP handshake is the only viable method to determine if the service is listening, or if you explicitly only wanted to monitor network connectivity rather than application health.
Live Migration is a Google Cloud infrastructure feature that automatically moves running virtual machines from one physical host to another without interrupting the guest operating system. It is primarily used by Google to perform transparent maintenance on the underlying hardware infrastructure.
You received an advanced notification of an impending physical hardware failure or scheduled host maintenance and needed to ensure your workload was moved to healthy hardware without experiencing a reboot.
Cloud Load Balancing uses health checks to probe backend instances at regular intervals. The primary function of these probes is to determine the routing of incoming network traffic. If an instance fails the health check, the load balancer marks it as unhealthy and stops sending new requests to it.
You only wanted to stop sending traffic to unresponsive instances and intended to rely on manual human intervention to identify and repair broken virtual machines, which violates the requirement for automated recovery.
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