What must be configured to accurately report an application ' s availability when onboarding a...

When onboarding a discovered private application behind a ZTNA Connector, the availability health check needs to validate that the application is actually reachable and responsive at the specific port and transport layer the application is served on, since an application can be fully down at the service layer while the underlying host still responds to a basic network-layer probe. A TCP-based ping/health check accomplishes this by attempting an actual TCP handshake against the application ' s configured port, which reflects the true availability of the service itself rather than just host-level network reachability — this is the accurate signal an administrator needs when reporting application availability, making option C correct. ICMP ping (option A) only confirms that the underlying host or IP is reachable at the network layer; a host can respond to ICMP echo requests while the specific application service on top of it is completely unavailable (crashed process, service not listening, port closed), making ICMP an unreliable and inaccurate proxy for application-level availability. HTTPS ping (option B) is protocol-specific and would misrepresent availability for the many private applications discovered by ZTNA Connector that are not HTTPS-based services at all, so it cannot serve as the general-purpose health check mechanism across arbitrary discovered applications. UDP ping (option D) is similarly protocol-mismatched for most discovered enterprise applications, which predominantly rely on TCP, and does not provide the accurate, connection-oriented confirmation that TCP-based health checking does.