The correct tool to use is the Advanced Startup Options menu, specifically the “Disable driver signature enforcement” startup setting. This is because the error “Windows cannot verify the publisher of this driver software” indicates that the driver lacks a valid digital signature, which 64-bit Windows 10 requires by default for driver installation. Temporarily disabling driver signature enforcement allows the unsigned driver to load for that single boot session, letting you install the trusted application without permanently weakening system security. On the CompTIA A+ Core 2 220-1202 exam, this scenario tests your knowledge of Windows recovery environments and driver signing policies—a common trap is choosing Device Manager or Group Policy, which cannot bypass the enforcement for a single boot. Remember: you must reboot into the Advanced Startup Options, not just change a setting in Windows. A helpful memory tip is “Boot to bypass”—you boot into the special menu to bypass the signature check for one session only.
220-1102 Windows OS Features and Tools Practice Question
This 220-1202 practice question tests your understanding of windows os features and tools. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A user on a Windows 10 computer is unable to install a new application because they receive an error that 'Windows cannot verify the publisher of this driver software.' The application is from a trusted vendor. Which tool should you use to temporarily disable driver signature enforcement to complete the installation?
This option in the Recovery Environment allows the system to boot with driver signature enforcement disabled, enabling installation of the driver.
D
Command Prompt with bcdedit /set testsigning on
Why wrong: While bcdedit can enable test signing mode, it is a more advanced step and not the typical tool for a one-time installation; the Advanced Startup option is simpler.
Option C is correct because the error 'Windows cannot verify the publisher of this driver software' indicates that the driver lacks a valid digital signature, which is required by default on 64-bit Windows 10. The Advanced Startup Options menu provides a direct way to boot with 'Disable driver signature enforcement' temporarily, allowing the unsigned driver to load for the current session without permanently altering the system's security policy.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Device Manager
Why it's wrong here
Device Manager can update or roll back drivers but cannot bypass driver signature enforcement.
✗
System Configuration (msconfig)
Why it's wrong here
System Configuration can enable Safe Mode but does not have a direct option to disable driver signature enforcement.
This option in the Recovery Environment allows the system to boot with driver signature enforcement disabled, enabling installation of the driver.
Related concept
Read the scenario before looking for a memorised answer.
✗
Command Prompt with bcdedit /set testsigning on
Why it's wrong here
While bcdedit can enable test signing mode, it is a more advanced step and not the typical tool for a one-time installation; the Advanced Startup option is simpler.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'bcdedit /set testsigning on' (which permanently enables test-signed drivers) with the temporary disable option in Advanced Startup Options, or they mistakenly think Device Manager or msconfig can override driver signature enforcement at the boot level.
Detailed technical explanation
How to think about this question
Driver signature enforcement is part of Windows Kernel-Mode Code Signing (KMCS) policy, which requires all kernel-mode drivers to have a valid Authenticode signature from a trusted certification authority. The 'Disable driver signature enforcement' option in Advanced Startup Options modifies the boot configuration data (BCD) for that single boot session by setting the 'nointegritychecks' flag, allowing unsigned drivers to load without permanently altering the BCD store. This is commonly used when installing legacy hardware or test drivers that lack a Microsoft-signed certificate.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 220-1202 question in full detail.
Windows OS Features and Tools — This question tests Windows OS Features and Tools — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Advanced Startup Options (Disable driver signature enforcement) — Option C is correct because the error 'Windows cannot verify the publisher of this driver software' indicates that the driver lacks a valid digital signature, which is required by default on 64-bit Windows 10. The Advanced Startup Options menu provides a direct way to boot with 'Disable driver signature enforcement' temporarily, allowing the unsigned driver to load for the current session without permanently altering the system's security policy.
What should I do if I get this 220-1202 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 220-1202 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1202 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.