220-1102 Question 360
Single answerActivate/deactivateA technician is preparing a Windows 11 laptop for a temporary contractor. The company wants the contractor to use the built-in local account named TempUser for two weeks, but the account must not be available after the contract ends. The technician wants the quickest method that preserves the profile and data so the account can be re-enabled later if needed. Which action should the technician take?
- A
Delete the TempUser account from Settings > Accounts
- B
Deactivate the TempUser account by disabling it in Local Users and Groups or with the appropriate command-line tool
- C
Remove TempUser from the Users group so the account cannot sign in
- D
Convert TempUser to a standard Microsoft account and then sign out
Show answer and explanation
Correct answer: B
Explanation
The best answer is to disable the local account rather than delete or alter it. In real-world support environments, deactivating an account is commonly used for temporary workers, leave of absence situations, or short-term access changes because it prevents login while preserving the user's profile and data. Microsoft administrative tools and best practices distinguish between disabling an account and deleting one: disabling is reversible, while deletion is intended for permanent removal. On Windows systems, local accounts can be disabled through Local Users and Groups on supported editions or by using supported local account management commands. This directly aligns with the objective of activate/deactivate account management in A+ Core 2.
- A. Incorrect.
Deleting the account removes access, but it is not the best choice for a temporary situation when the company wants to preserve the profile and data for possible later use. Re-creating the account later would not be the same as simply reactivating it, and the user's existing local profile association may be lost or require manual recovery.
- B. Correct.
This is correct. Disabling a local account deactivates sign-in without deleting the account's profile and associated data. In Windows editions that support it, this can be done through Local Users and Groups, or by using supported command-line methods such as disabling the account with a local user management command. This is the preferred approach when the account may need to be activated again later.
- C. Incorrect.
Removing TempUser from the Users group is not the correct method for deactivating an account. It may affect permissions, but it does not reliably disable sign-in in the intended administrative way. It also introduces unnecessary permission issues instead of using the built-in account disable function designed for this purpose.
- D. Incorrect.
Converting the account type does not deactivate it. Changing to a Microsoft account changes how the user authenticates, but it does not meet the requirement to temporarily block access while preserving the account for later reactivation.