Which monitor should be used to verify the availability of an e-commerce solution that uses backend SQL and RADIUS, with a status page on port 99?

Which monitor should be used to verify the availability of an e-commerce solution that uses backend SQL and RADIUS, with a status page on port 99?

• A. HTTP on port 99
• B. HTTP-ECV on port 80
• C. HTTP on port 80
• D. HTTP-ECV on port 99

Answer: (D)

The key idea is using a health check that not only reaches the service but also verifies that the status page shows healthy content on a nonstandard port. An HTTP-ECV monitor is designed for this: it fetches the status page and validates specific content (for example, a “Healthy” indicator or expected metrics), giving you confidence that the e-commerce backend (including SQL and RADIUS) is actually functioning. Since the status page lives on port 99, configuring HTTP-ECV to use port 99 ensures you’re checking the correct endpoint and validating its content, not just attempting a generic HTTP connect. An HTTP monitor on a standard port or an HTTP-ECV on a different port wouldn’t reliably verify the status page on 99, so the HTTP-ECV on port 99 is the appropriate choice.

The key idea is using a health check that not only reaches the service but also verifies that the status page shows healthy content on a nonstandard port. An HTTP-ECV monitor is designed for this: it fetches the status page and validates specific content (for example, a “Healthy” indicator or expected metrics), giving you confidence that the e-commerce backend (including SQL and RADIUS) is actually functioning. Since the status page lives on port 99, configuring HTTP-ECV to use port 99 ensures you’re checking the correct endpoint and validating its content, not just attempting a generic HTTP connect. An HTTP monitor on a standard port or an HTTP-ECV on a different port wouldn’t reliably verify the status page on 99, so the HTTP-ECV on port 99 is the appropriate choice.