2V0-621 · Question #33
An administrator is configuring the clock tolerance for the Single Sign-On token configuration policy and wants to define the time skew tolerance between a client and the domain controller clock. Whic
The correct answer is A. Milliseconds. The clock tolerance value in vCenter SSO token configuration is specified in milliseconds to define the acceptable time skew between client and domain controller.
Question
An administrator is configuring the clock tolerance for the Single Sign-On token configuration policy and wants to define the time skew tolerance between a client and the domain controller clock. Which time measurement is used for the value?
Options
- AMilliseconds
- BSeconds
- CMinutes
- DHours
How the community answered
(48 responses)- A88% (42)
- B4% (2)
- C2% (1)
- D6% (3)
Why each option
The clock tolerance value in vCenter SSO token configuration is specified in milliseconds to define the acceptable time skew between client and domain controller.
VMware vCenter SSO token policy uses milliseconds as the unit for the clock tolerance field, which controls the maximum acceptable time difference between the client and the domain controller clock during token validation. This fine-grained unit allows precise synchronization control to prevent replay attacks while accommodating minor drift.
Seconds is not the unit used for this field - the SSO token configuration clock tolerance value is entered in milliseconds, not seconds.
Minutes is not the unit used - the clock tolerance field in SSO token policy accepts milliseconds, not minutes.
Hours is not the unit used - the SSO token configuration clock tolerance is measured in milliseconds, not hours.
Concept tested: vCenter SSO token policy clock tolerance units
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-authentication/GUID-2FD5AE2C-2E72-4BC1-BBF0-5E5793CD4A81.html
Topics
Community Discussion
No community discussion yet for this question.