Question 380
Before approving a proposed shortcut for the following case—A laptop must authenticate pre-login so machine startup scripts reach a required domain service before the user signs in—which risk should be considered first?
Explanation
Correct Answer
The issue is not a general product inconvenience: User-logon-only tunnels cannot guarantee connectivity before a user session exists. That matters for a laptop must authenticate pre-login so machine startup scripts reach a required domain service before the user signs in. The design should document the corresponding investigation and practical acceptance evidence.
Incorrect Answers
Applying this option would direct attention to a contractor VPN should be used only when accessing approved private apps; forced tunnel from boot disrupts other permitted work. In the reported design—a laptop must authenticate pre-login so machine startup scripts reach a required domain service before the user signs in—the needed risk statement is user-logon-only tunnels cannot guarantee connectivity before a user session exists.
The alternative deals with “remote users lose access during identity transition between machine pre-logon and user-logon states”. Confirm the relevant evidence—inspect machine and user authentication, tunnel handoff and route persistence during login—before selecting architect a supported pre-logon-to-user session transition with tested identity policy. The current question instead selects “User-logon-only tunnels cannot guarantee connectivity before a user session exists”.
The option applies in “an enterprise wants VPN protection automatically whenever users sign in, but currently expects them to click Connect”. The expected safe result is that the test user obtains the required tunnel at logon without manual initiation. That evidence does not directly establish “User-logon-only tunnels cannot guarantee connectivity before a user session exists” for the scenario at hand.