Some company employees are able to print documents when working from home, but not on network-attached printers, while others are able to print only to file. What can be inferred about the affected…

Question

Options

• AThey may be attached to the default extensions policy and profile
• BThey may have a host firewall profile set to block activity to all network-attached printers
• CThey may have different disk encryption profiles that are not allowing print jobs on encrypted files
• DThey may be on different device extensions profiles set to block different print jobs

• A
  4% (2)
• B
  71% (34)
• C
  17% (8)
• D
  8% (4)

Explanation

Option B is correct because host-based firewall profiles (e.g., Windows Firewall's Domain/Private/Public profiles) apply different rules depending on the network the device detects - when employees work from home, their device may switch to a more restrictive profile that blocks outbound traffic on printer ports (e.g., TCP 9100, 515), preventing access to network-attached printers; users who can only print to file have an even more restrictive profile blocking all printer network traffic. Option A is wrong because a "default extensions policy" is too generic and doesn't explain a specific network printing failure. Option C is wrong because disk encryption operates at the file system level and has no bearing on whether print jobs can be routed to a network printer. Option D is wrong because "device extensions profiles blocking different print jobs" doesn't logically map to the network-layer distinction between printing to a file versus a network-attached printer.

Memory tip: When remote workers lose access to network resources specifically, think firewall profile first - the device's network location detection triggers a stricter firewall profile at home (Public) vs. the office (Domain), and that profile can silently block printer ports.

No community discussion yet for this question.