nerdexam
CompTIA

220-1102 · Question #524

A technician wants to update the local security policies on a Windows machine but is unable to launch the expected snap-in. Which of the following is the most likely reason?

The correct answer is A. The computer is running Windows Home. The most likely reason a technician cannot launch the local security policy snap-in is that the computer is running Windows Home, which does not include this feature.

Operating Systems

Question

A technician wants to update the local security policies on a Windows machine but is unable to launch the expected snap-in. Which of the following is the most likely reason?

Options

  • AThe computer is running Windows Home.
  • BThe user did not sign the end user license agreement.
  • CThe user disabled the User Account Control.
  • DAn antivirus application is blocking access.

How the community answered

(16 responses)
  • A
    94% (15)
  • C
    6% (1)

Why each option

The most likely reason a technician cannot launch the local security policy snap-in is that the computer is running Windows Home, which does not include this feature.

AThe computer is running Windows Home.Correct

Windows Home editions (e.g., Windows 10 Home, Windows 11 Home) do not include the Local Security Policy Editor (secpol.msc) snap-in, as it is a feature reserved for Professional, Enterprise, and Server editions. This missing component prevents the technician from launching it.

BThe user did not sign the end user license agreement.

Not signing an End User License Agreement (EULA) would prevent the operating system from installing or running correctly in the first place, not specifically block a snap-in after installation.

CThe user disabled the User Account Control.

Disabling User Account Control (UAC) might reduce security prompts but would not remove or block access to a core system snap-in if it exists on the system.

DAn antivirus application is blocking access.

While an antivirus application could potentially interfere with system processes, it is highly unlikely to completely block the launch of a standard Windows administrative snap-in without providing a specific warning or error, especially for a feature that simply doesn't exist in Home editions.

Concept tested: Windows edition features (Local Security Policy Editor)

Source: https://www.microsoft.com/en-us/windows/compare-windows-11-home-vs-pro

Topics

#Windows editions#Local Security Policy#MMC snap-ins

Community Discussion

No community discussion yet for this question.

Full 220-1102 Practice