Question 180
At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. Which control best prevents this particular failure from recurring?
Explanation
Correct Answer
Monitor certificate expirations and trust-chain changes with automated predeployment verification. This prevents the recurrence because tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. A matching immediate correction is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Applied here, the relevant facts are: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. The question asks which control best prevents this particular failure from recurring.
Incorrect Answers
That test belongs to another control with this basis: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. In the current case, the governing reason is: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The direct verification is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.
This observation would test a different technical dependency: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The current issue is governed by: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Its decisive check is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.
The alternative verifies a different condition: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The current case instead depends on: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Confirm that “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.