You need to configure a Deployment on Google Kubernetes Engine (GKE). You want to include a check that verifies that the containers can connect to the database. If the Pod is failing to connect, you w

Question

Options

• ACreate two jobs: one that checks whether the container can connect to the database, and another
• BCreate the Deployment with a livenessProbe for the container that will fail if the container can't
• CCreate the Deployment with a PostStart lifecycle handler that checks the service availability.
• DCreate the Deployment with an initContainer that checks the service availability. Configure a

• A
  12% (7)
• B
  80% (48)
• C
  5% (3)
• D
  3% (2)

Explanation

A livenessProbe continuously checks whether a running container is still healthy. Configuring it to test database connectivity means Kubernetes will detect the failure. To run a graceful shutdown script before the container is terminated, you add a preStop lifecycle hook - Kubernetes executes this hook before sending SIGTERM, giving the application time to clean up. This combination directly satisfies both requirements. Jobs (A) are for batch workloads and not suited for continuous health monitoring. A postStart handler (C) runs immediately after container start and is not re-evaluated during the container's lifetime. An initContainer (D) runs only once before the main container starts and cannot continuously monitor a live connection.

No community discussion yet for this question.