Examkin

Question

Difficulty: Very hardWindows Client Networking Configuration

A field technician is configuring a Windows 11 Pro laptop for a workstation operating on a secure local subnet. The corporate firewall requires all client network interfaces to be categorized correctly to enforce network isolation policies. When the laptop connects to the internal office Wi-Fi network, Windows Network Location Awareness (NLA) classifies the connection as a Public network. As a result, network discovery is disabled and local printer access is blocked, even though the client has acquired a valid static IPv4 address. Which procedure in Windows 11 is the most direct and proper method to reclassify this connection profile to Private without creating custom firewall port exceptions?

  1. Navigate to Settings > Network & internet > Wi-Fi, select the connected network properties, and change the Network profile type to Private.Answer
  2. B
    Open Network Connections (ncpa.cpl), open the Wi-Fi Properties window, select TCP/IPv4 Properties, click Advanced, and select 'Enable NetBIOS over TCP/IP' on the WINS tab.
  3. C
    Open Windows Defender Firewall with Advanced Security, navigate to Inbound Rules, and select 'Enable All Domain Rules' for the Wi-Fi interface.
  4. D
    Open an elevated Command Prompt and execute the command ipconfig /setprofile "Wi-Fi" private.

Answer

Navigating to Settings > Network & internet > Wi-Fi, opening the active network properties, and selecting the Private network profile type.
In Windows 11, Network Location Awareness (NLA) automatically assigns a network category (Public or Private) to each network connection. The Public profile disables Network Discovery and File/Printer Sharing for security on untrusted networks. Changing the Network profile type to Private under Network & internet settings informs Windows Firewall that the local subnet is trusted, automatically allowing local discovery and printer sharing without creating manual firewall rule exceptions.

Step-by-Step Solution

1
Identify the cause of blocked network discovery and local file/print sharing.
Recognize that Windows Network Location Awareness (NLA) has assigned the 'Public' network profile to the connection, causing Windows Defender Firewall to block inbound local subnet discovery.
Public profiles enforce strict isolation policies by turning off Network Discovery and File and Printer Sharing by default.
2
Select the correct administrative interface to adjust the connection profile.
Access the Windows 11 Settings app under Network & internet > Wi-Fi (or Ethernet) > Network Properties.
Network profile classification (Public vs. Private) is managed per-interface via NLA properties in the Settings app or via PowerShell (Set-NetConnectionProfile).
3
Switch the profile type from Public to Private.
The Private profile is applied, enabling standard network discovery and local subnet sharing rules in Windows Defender Firewall.
This resolves local resource accessibility without requiring manual firewall port exception overrides.

Key Concept

Windows Network Location Awareness (NLA) and Network Profile Types (Public vs. Private)
Rate this question

Topics

Windows Client Networking Configuration

More questions from this topic