Where can you check that the LDAP binding is using TCP/636?

The configuration for LDAP integration, including the directory hosts and the specific port used for communication, is managed within the PVWA interface. An administrator can verify that the binding is configured to use TCP/636 (LDAPS) by navigating to the LDAP Integration settings, selecting the relevant directory, and inspecting the "Host" details. This section explicitly contains the IP/hostname and the port number for the connection to the domain controller.

A. This configuration path does not exist in Active Directory. CyberArk's LDAP binding configuration is stored within the CyberArk Vault, not in AD object properties.

C. LDAP Directory Mapping is configured through the PVWA web interface, not the PrivateArk Client, which is used for core Vault administration tasks.

D. Test-NetConnection is a PowerShell command used to test network connectivity from the PVWA server. It can confirm if a port is open but does not show how CyberArk is configured to use that port.

1. CyberArk Privileged Access Manager - Self-Hosted Documentation v14.0. "Configure LDAP integration". In the "Define directory hosts" step

the documentation states: "In the Host details area

in Port

specify the port number that is used to connect to the directory host. The default port is 389 for LDAP and 636 for LDAPS." This confirms the setting is located under the Host configuration in the PVWA's LDAP Integration section.

2. CyberArk Privileged Access Manager - Self-Hosted Documentation v13.2. "LDAP Integration". The procedure outlines the navigation path: "In the PVWA

click the Administration button

and then click LDAP Integration... In the Directories tab

select the directory to configure... In the Hosts tab

click Add host... In the Host details area

in Port

specify the port number...". This directly corresponds to the path described in option B.