220-1102 Question 185
Single answerPublic network vs. private networkA technician is configuring a Windows 11 laptop for an employee who normally works in the office but is traveling this week. The user needs to connect to hotel Wi-Fi to access email and browse the web. In the office, the laptop must still be discoverable for file sharing and remote management by the IT team. Which network profile should the technician recommend the user select when connecting to the hotel Wi-Fi?
- A
Public network, because it reduces device discoverability and is more appropriate for untrusted networks
- B
Private network, because it allows easier file sharing and helps the laptop reconnect faster
- C
Domain network, because the user signs in with company credentials and needs access to corporate resources
- D
Guest network, because Windows automatically applies stricter firewall rules than Public
Show answer and explanation
Correct answer: A
Explanation
The best answer is Public network. A+ Core 2 expects technicians to understand the practical security implications of Windows network profiles. Public should be used on untrusted or shared networks because it restricts discoverability and sharing. Private is appropriate only on trusted local networks where the organization or user wants easier device discovery, printer access, or file sharing. Domain is automatically applied in managed enterprise environments when the device can identify the domain network. Microsoft documentation for Windows network profiles and Defender Firewall behavior supports this distinction: Public is the safer setting for hotels, airports, and other shared networks, while Private is intended for trusted environments.
- A. Correct.
Correct. On Windows, the Public network profile is intended for untrusted networks such as hotel, airport, or coffee shop Wi-Fi. It typically disables network discovery and limits sharing exposure, reducing the chance that other devices on the same network can see or access the laptop. This is the safest choice for a temporary connection on a shared external network.
- B. Incorrect.
Incorrect. The Private network profile is meant for trusted networks such as a home network or a small office where discovery and sharing may be appropriate. Selecting Private on hotel Wi-Fi would unnecessarily increase exposure to other devices on the same shared network. A candidate might choose this because the user still needs corporate access, but network profile selection is based on trust of the local network, not on whether the user needs internet access or company applications.
- C. Incorrect.
Incorrect. Domain network is not something a user manually selects based on travel or location. In Windows, a Domain profile is applied when the system detects and authenticates to an Active Directory domain environment. A hotel Wi-Fi network does not become a Domain network just because the user logs in with company credentials or uses cloud services.
- D. Incorrect.
Incorrect. "Guest network" is a common wireless router feature, not a standard Windows network profile choice in this context. Windows network location types relevant here are generally Public, Private, and Domain when domain-joined and detected. Someone might pick this because guest wireless networks are often restricted, but that is a router-side SSID configuration, not the Windows profile the technician is choosing.