Which Citrix ADC monitor can verify the authentication service of the Active Directory domain controller?

• A. A TCP monitor with the LDAP Base DN configured in the basic parameters.
• B. An LDAP monitor with the LDAP Script Name, Configured Base DN, Bind DN, Filter, Attribute, and Password parameters in the basic parameters.
• C. A MYSQL-ECV monitor with the Base DN, Bind DN, Filter, Attribute, and Password parameters configured in the basic parameters.
• D. A ping monitor with the IP address of the AD domain controller in the special parameters.

Answer: (B)

To verify the Active Directory authentication service, you need a monitor that actually speaks LDAP and can exercise a real authentication flow against the domain controller. An LDAP monitor does exactly that: it can perform a bind using a Bind DN and password, start searches from a configured Base DN, apply a Filter to locate a user, and verify the returned Attribute values. The LDAP Script Name lets you tailor the LDAP transaction to simulate a typical authentication scenario, ensuring the domain controller not only responds but also authenticates credentials correctly. This is the right approach because it tests the exact service consumers rely on, not just network reachability.

In contrast, a TCP monitor would only check that the LDAP port is open, not that authentication works. A MySQL-ECV monitor is unrelated to directory services, and a ping monitor checks basic reachability via ICMP, not LDAP functionality.