In a PingAM cluster, debug levels are configured dynamically through the administrative console on a per-server (instance) basis. This allows an administrator to enable detailed logging for a specific service on a single server to troubleshoot an issue without affecting the performance of other servers in the cluster. The settings are stored in the configuration data store and applied to the selected server instance, providing granular control over logging.

A. Editing debug.properties directly is not the recommended method in a cluster, as changes can be overwritten by the central configuration.

C. Debug levels are set at the more granular server-instance level, not for an entire site, which is a logical grouping of servers.

D. Changing debug levels is a fundamental and necessary administrative task for diagnosing and resolving issues in any environment.

1. Ping Identity, PingAM Documentation, "Setup and Maintenance Guide," Chapter: "Monitoring Servers," Section: "To Configure Debug Logging for Troubleshooting." This section details the process of setting debug levels for specific services on individual servers through the admin console.

2. Ping Identity, PingAM Documentation, "Administration Guide," Chapter: "Server and Site Configuration," Section: "Configuring Server Defaults." This section explains that debug settings are part of the server-specific configuration managed within the UI.