Scenario: A Citrix Administrator is running an e-commerce web service that uses backend SQL and Radius servers. The e-commerce platform runs on a web server using port 80, and a website status page…

Question

Options

• AHTTP-ECV on port 80
• BHTTP on port 80
• CHTTP-ECV on port 99
• DHTTP on port 99

• A
  4% (1)
• B
  4% (1)
• C
  8% (2)
• D
  84% (21)

Explanation

Option D is correct because port 99 hosts the website status page, which already aggregates and reports the health of all servers in the solution - including the web server, SQL, and Radius backends. Monitoring port 99 with a standard HTTP monitor confirms that this status page is reachable, giving the administrator a single check that reflects the availability of the entire e-commerce platform.

Why the distractors fail:

• A & B (port 80): Monitoring the web server directly only confirms the web tier is up - it reveals nothing about whether the SQL or Radius servers are functioning.
• C (HTTP-ECV on port 99): HTTP-ECV (Extended Content Verification) goes further by scanning the response body for specific strings; that's unnecessary overhead here since no content string check is required - we just need to know the status page is accessible.

Memory tip: Think of port 99 as the "control room" - it already watches all the servers for you, so one HTTP check there tells you everything. HTTP-ECV is for when you need to read what the page says; HTTP is for when you just need the page to answer.

No community discussion yet for this question.