CV0-003 · Question #8
Ann. a user, has tried to connect to a VM hosted in a private cloud using her directory services credentials. After three attempts, she realizes the keyboard was set to German instead of English…
The correct answer is E. The account localization settings are incorrect. Ann typed the wrong password three times because her keyboard was set to German (y and z are swapped on German vs. English layouts). She then changed her local keyboard setting and tried again but still cannot log in, while other users can. The critical detail is that fixing…
Question
Ann. a user, has tried to connect to a VM hosted in a private cloud using her directory services credentials. After three attempts, she realizes the keyboard was set to German instead of English, and she was typing "z" instead of "y". After fixing this issue, Ann is still unable to log in; however, other users can access the VM. Which of the following is the MOST likely cause?
Options
- AThe default language on Ann's computer is German.
- BThe account was locked.
- CDirectory services are offline.
- DThere is an account mismatch.
- EThe account localization settings are incorrect.
How the community answered
(60 responses)- A12% (7)
- B2% (1)
- C7% (4)
- D2% (1)
- E78% (47)
Explanation
Ann typed the wrong password three times because her keyboard was set to German (y and z are swapped on German vs. English layouts). She then changed her local keyboard setting and tried again but still cannot log in, while other users can. The critical detail is that fixing the local or OS-level keyboard does not correct the localization settings stored within Ann's account profile on the VM or in directory services. If her account's locale is still configured as German, the authentication system processes her keystrokes using German keyboard mapping, so the same character transposition persists regardless of her physical keyboard. Other users are unaffected because their accounts have correct localization. Option B (account lockout) is the most common distractor-three failed attempts often triggers lockout-but the question's framing traces the root cause to the keyboard/locale issue, and a lockout would be a symptom, not the underlying misconfiguration. Option C is ruled out because other users can successfully authenticate, confirming directory services are online.
Topics
Community Discussion
No community discussion yet for this question.