When validating authentication methods for each type of system component, what must be observed?

• A. An authentication event that functions in accordance with the documented method.
• B. No verification required.
• C. The authentication data must be in plaintext.
• D. Authentication must be bypassed if the system is busy.

Answer: (A)

Validating authentication methods for each system component hinges on confirming that an authentication event occurs and operates exactly as the documented method prescribes. This shows the implemented method is actually in use and enforcing access controls as intended, rather than being merely described. Observing a real authentication interaction (such as a login, token exchange, or certificate-based handshake) that follows the documented steps, protections, and flow validates that the system component authenticates users or devices correctly. The other options do not fit: there must be verification to confirm the method works; authentication data should never be in plaintext because credentials must be protected in transit and at rest; and bypassing authentication when the system is busy would undermine security and violate access-control requirements.