CompTIA A+

• Unit 01

  A+ Core 1 (220-1201)

  Access: Free tier
  2,172 questions · 34 topics
• Unit 02

  A+ Core 2 (220-1202)

  Access: Premium
  2,253 questions · 30 topics

A few questions from this module, with the answer and a full explanation. The complete bank is available when you start practising.

1. A technician is reviewing a Windows disk layout in Disk Management and notices a 500 MB partition labelled 'System Reserved' that is marked as Active. What is the function of this partition?

   • A
     It contains the Windows Boot Manager and BCD store required to initiate the Windows boot process
     Correct answer
   • B
     It reserves disk space for future Windows feature update installations
   • C
     It contains the WinRE recovery tools used for system repair and reset operations
   • D
     It contains the Windows hibernation file (hiberfil.sys) and page file
   Explanation

   The 'System Reserved' partition is the system partition that Windows creates automatically during installation on MBR disks. Marked as Active, it stores the Windows Boot Manager (bootmgr) and the Boot Configuration Data (BCD) store — the files the firmware hands control to after POST. Without it, the OS cannot load. It is distinct from the recovery partition (which stores WinRE) and from the boot partition (which stores C:\Windows). Key takeaway: the 'System Reserved' partition = Windows Boot Manager + BCD = required for starting Windows.

2. A technician is investigating repeated application crashes on a workstation used by multiple users. The crashes only occur for one specific user account, not for others. Event Viewer for that user shows 'faulting module: app_plugin.dll, version 1.2.0.0'. Other users' sessions show the same plugin loading at version 2.1.0.0. Which is the MOST likely cause?

   • A
     The affected user recently ran sfc /scannow which downgraded app_plugin.dll to its original version 1.2.0.0
   • B
     The affected user has a per-user installation or cached copy of app_plugin.dll version 1.2.0.0 in their user profile directory, which takes precedence over the newer system-wide version
     Correct answer
   • C
     The affected user's antivirus profile is blocking DLL version 2.1.0.0 and substituting version 1.2.0.0 from a quarantine cache
   • D
     Windows applies DLL version assignment randomly per user session as part of its load-balancing feature
   Explanation

   Windows DLL search order checks the application's directory, then per-user paths (such as %APPDATA% or the user's profile), before falling back to system directories. If an older version of the DLL exists in the user's profile directory from a previous per-user installation or manual copy, it will be loaded in preference to the newer system-wide version. This explains why only one user is affected. The fix is to remove or update the DLL in the user's profile directory. The key takeaway: per-user DLL copies in profile directories can override system-wide versions due to DLL search order — check the affected user's profile for conflicting DLL copies when only one user is affected.

3. A user complains they cannot access the internet or any shared network resources. A technician runs ipconfig and sees the IP address is 169.254.30.5. The technician confirms the Ethernet cable is plugged in and the link light is active. What is the most appropriate next troubleshooting step?

   • A
     Configure a static IP address in the 169.254.0.0 range to stabilise the connection
   • B
     Run ipconfig /release and ipconfig /renew to attempt to obtain a valid IP address from the DHCP server
     Correct answer
   • C
     Run ipconfig /flushdns to clear the DNS cache, which is preventing DHCP from responding
   • D
     Change the network profile from Public to Private to allow DHCP traffic through the firewall
   Explanation

   A 169.254.x.x APIPA address confirms DHCP has failed. With physical connectivity confirmed (cable and link light), the issue is likely a DHCP communication problem. Running ipconfig /release drops any current lease attempt and /renew forces a fresh DHCP discovery. If /renew fails, the technician can then investigate the DHCP server. Key takeaway: APIPA + physical link = DHCP failure; always try ipconfig /release and /renew before investigating deeper DHCP issues.