Question 620
An enterprise access-control incident describes: A site-wide posture rollout floods users with reassessment prompts every few minutes because a lease or refresh setting was made too short. Which statement best explains why the correct response works?
Explanation
Correct Answer
Posture lease and synchronization intervals influence when endpoints repeat health checks; excessively short intervals create avoidable churn. This behavior directly governs the stated requirement. The recommended action is: Tune supported posture lease and reassessment settings according to security policy and observed operational behavior. The acceptance result is: Pilot devices maintain a stable compliant state while required periodic validation continues at the intended interval.
Incorrect Answers
Simulate posture PSN loss during high-availability acceptance testing. The repeat risk here is different: Retain condition-level posture evidence with high-impact access-denial tickets. A directly relevant preventive control is: Posture lease and synchronization intervals influence when endpoints repeat health checks; excessively short intervals create avoidable churn.
The offered option specifies “RADIUS authentication visibility alone does not prove posture workflows were invoked or completed”. The question requires “Posture lease and synchronization intervals influence when endpoints repeat health checks; excessively short intervals create avoidable churn”: Retain condition-level posture evidence with high-impact access-denial tickets. These are not equivalent responses to the stated requirement.
The test client reports a completed posture state once agent and PSN communication is restored, with password validation unchanged. The repeat risk here is different: Retain condition-level posture evidence with high-impact access-denial tickets. A directly relevant preventive control is: Posture lease and synchronization intervals influence when endpoints repeat health checks; excessively short intervals create avoidable churn.