Study CompTIA 220-1202 Networking, Filesystems, and Accounts: key concepts, common traps, and exam decision cues.
Core 2 operating-systems questions also test the edge where Windows client settings meet identity, networking, and filesystem behavior. These are the questions where candidates know the tools but still misread the scope.
Workgroup: A local peer-style management model without centralized domain identity and policy control.
Metered connection: A network setting that treats bandwidth as limited and can change update and sync behavior.
The exam usually wants you to:
| If the prompt is really about… | Strongest first reading |
|---|---|
| home or small unmanaged device | local or Microsoft account behavior |
| scripts, home folders, folder redirection, or Group Policy | domain-managed identity and policy path |
| shared drives and printers in a business environment | domain vs workgroup distinction before random reinstall work |
| one user, one device, one local setting | do not over-assume domain complexity |
| Symptom or clue | Strongest first lane |
|---|---|
| cannot reach file server or mapped drive | DNS, gateway, VPN path, resource path, credentials, and domain reachability |
| shared printer works for some users but not one client | shared-resource path, profile, permission, or client config |
| issue appears only on public Wi-Fi | network profile, proxy, VPN, and firewall behavior |
| user complains updates or sync are delayed on mobile hotspot | metered-connection behavior may be intentional |
| wired vs wireless confusion in the stem | read it as connection-path selection before app repair |
| Filesystem | Strongest exam-useful recall |
|---|---|
| NTFS | Windows-first permissions and common desktop support path |
| ReFS | resilience-focused Windows storage context rather than ordinary consumer removable-media usage |
| FAT32 | older compatibility with meaningful file-size limits |
| exFAT | removable-media and cross-platform compatibility path |
| APFS | modern Apple filesystem path |
| ext4 and XFS | Linux filesystem context |
| Trap | Better reading |
|---|---|
| assuming a mapped-drive problem is always NTFS | network path, credentials, VPN, DNS, and share path still matter first |
| forgetting public vs private profile behavior | Windows profile choice can change firewall and discovery behavior |
| treating metered behavior as random failure | reduced sync or update behavior may be expected |
| using domain logic on a standalone machine | confirm whether the device is domain-joined or not |
flowchart LR
A["Read user and device scope"] --> B["Local, Microsoft, or domain account?"]
B --> C["Check connection path: wired, wireless, or VPN"]
C --> D["Check client config: IP, DNS, gateway, proxy, profile"]
D --> E["Verify resource path, permission, and filesystem fit"]
A remote user can sign in locally but cannot reach a company file share after switching from office Ethernet to hotel Wi-Fi. Which answer best fits Core 2?
Correct answer: B. The clue points to client networking and resource path changes, not to local storage corruption or unrelated hardware.