220-1102 Practice Question: A company uses a login script that sets…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The script runs too early before the network is fully initialized

  Why it's wrong here

  The script running prematurely before network initialization can indeed cause intermittent drive mapping failures. This occurs when the network stack, DNS resolution, or domain controller authentication services are not fully operational at the exact moment the script attempts to connect to network shares. The timing can vary slightly between logons or system loads, leading to a race condition where sometimes the network resources are available for mapping, and other times they are not, resulting in inconsistent success.

• ✓

  The department codes in the script do not match the actual codes due to case sensitivity

  Why this is correct

  Batch script 'IF' comparisons, by default, are case-sensitive. If a login script uses a conditional statement like 'IF "%DEPARTMENT%"=="Sales"' to map a drive, but a user's actual department attribute is stored as "sales" or "SALES" in Active Directory, the condition will evaluate as false. This mismatch prevents the drive mapping for those specific users, explaining why some users experience successful mappings while others, whose department codes differ only in case, do not, leading to intermittent failures across the user base.

• ✗

  The script is using 'setx' instead of 'set' for environment variables

  Why it's wrong here

  Using 'SETX' in a login script creates a persistent environment variable that remains active across user sessions and system reboots, unlike 'SET', which creates a temporary variable for the current session only. While 'SETX' might not be the intended command for a session-specific drive mapping script, its use would not cause intermittent drive mapping failures. The persistent variable would either consistently enable or consistently prevent the mapping based on its value, rather than exhibiting sporadic behavior.

• ✗

  The user accounts lack permission to run login scripts

  Why it's wrong here

  If user accounts genuinely lacked the necessary permissions to execute login scripts, the problem would manifest as a consistent and complete failure for all affected users every time they logged in. Permissions are typically binary and apply uniformly, meaning the script would either always run or always fail. The scenario describes intermittent drive mapping failures, which points away from a fundamental permission issue and towards a conditional or timing-dependent problem within the script's execution logic.

Go deeper

Related to this question