220-1102 · Question #52
A user is unable to log in to the domain with a desktop PC, but a laptop PC is working properly on the same network. A technician logs in lo the desktop PC with a local account but is unable to…
The correct answer is A. Time drift. The most likely cause for a desktop PC failing to log into a domain and access secure intranet sites, while a laptop on the same network works, is time drift.
Question
A user is unable to log in to the domain with a desktop PC, but a laptop PC is working properly on the same network. A technician logs in lo the desktop PC with a local account but is unable to browse to the secure intranet site to get troubleshooting tools. Which of the following is the MOST likely cause of the issue?
Options
- ATime drift
- BDual in-line memory module failure
- CApplication crash
- DFilesystem errors
How the community answered
(35 responses)- A80% (28)
- B3% (1)
- C6% (2)
- D11% (4)
Why each option
The most likely cause for a desktop PC failing to log into a domain and access secure intranet sites, while a laptop on the same network works, is time drift.
Dual in-line memory module (DIMM) failure would likely cause system crashes, reboots, or blue screens, not specifically prevent domain login while allowing local login and network access.
An application crash affects a specific application, not the fundamental ability to log into a domain or browse secure network resources system-wide.
Filesystem errors could cause various issues, including application failures or boot problems, but they are less directly tied to the specific symptoms of failing domain authentication and secure intranet browsing while allowing local login and basic network connectivity than time drift.
Concept tested: Domain authentication troubleshooting - time synchronization
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/kerberos-authentication-issues-time-skew
Topics
Community Discussion
No community discussion yet for this question.