Question 101 of 1,152
Security ArchitecturemediumMultiple SelectObjective-mapped

Quick Answer

The answer is Secure Boot and application allowlisting. Secure Boot is a UEFI firmware feature that cryptographically verifies the bootloader’s digital signature against a trusted database stored in the firmware, which prevents the system from booting from any untrusted external media like a USB drive that lacks a valid signature. Application allowlisting, often enforced through Windows AppLocker or WDAC, creates a policy that only permits pre-approved executables, scripts, or installers to run, blocking all unapproved software. On the Security+ SY0-701 exam, this pairing tests your understanding of layered endpoint security controls: one at the firmware level to lock down the boot process, and one at the OS level to control runtime execution. A common trap is confusing Secure Boot with TPM or BitLocker—remember that Secure Boot protects the boot chain, not disk encryption. For a memory tip, think “Boot and Block”: Secure Boot locks the boot path, and allowlisting blocks unapproved apps.

SY0-701 Security Architecture Practice Question

This SY0-701 practice question tests your understanding of security architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 help desk manager is hardening a fleet of Windows laptops. The goal is to prevent booting from untrusted external media and to ensure only approved software can run on the devices. Which two controls best address those goals? Select two.

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

Question 1mediummulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Enable Secure Boot in firmware.

Secure Boot is a UEFI firmware feature that verifies the digital signature of the bootloader against a database of trusted signatures stored in the firmware. By enabling Secure Boot, the system will refuse to boot from any external media (e.g., USB drives) that does not have a valid, trusted signature, directly preventing unauthorized boot code from executing.

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.

  • Enable Secure Boot in firmware.

    Why this is correct

    Secure Boot helps ensure the device only starts trusted boot components that are signed by a trusted key. That reduces the risk of booting unapproved loaders or malicious recovery media. It is a platform hardening control that directly addresses firmware-level trust during startup, which is exactly what the scenario calls for.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Implement application allowlisting or application control.

    Why this is correct

    Application allowlisting controls which programs can execute on the endpoint, so only approved software runs. This is the correct control when the goal is to prevent unsanctioned utilities from launching after the system boots. Combined with Secure Boot, it covers both startup integrity and runtime execution restrictions.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Rely only on full-disk encryption to stop unauthorized boot code.

    Why it's wrong here

    Full-disk encryption protects data at rest, but it does not stop a machine from attempting to boot untrusted media. An attacker could still boot into alternate code if firmware settings are weak. Encryption is valuable, but it does not solve the specific boot-control problem described here.

  • Increase the screen-lock timeout so users are interrupted less often.

    Why it's wrong here

    Screen lock timing affects idle-session exposure, not startup trust or software execution. It may be useful for operational convenience, but it does nothing to stop unauthorized boot devices or unapproved applications. The scenario requires platform hardening, not a user-inactivity setting.

  • Use a stronger Wi-Fi password so malware cannot start.

    Why it's wrong here

    Wi-Fi password strength does not control firmware boot behavior or local application execution. Malware can start from many other pathways, and wireless credentials do not substitute for endpoint hardening. This option addresses the wrong layer of the system.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse full-disk encryption with boot security, mistakenly thinking encryption prevents unauthorized boot media, when in fact encryption only protects data confidentiality and does not control the boot process or software execution.

Trap categories for this question

  • Scenario analysis trap

    Screen lock timing affects idle-session exposure, not startup trust or software execution. It may be useful for operational convenience, but it does nothing to stop unauthorized boot devices or unapproved applications. The scenario requires platform hardening, not a user-inactivity setting.

Detailed technical explanation

How to think about this question

Secure Boot relies on the UEFI firmware's signature database (db) and forbidden signature database (dbx). When a bootloader is loaded, its signature is checked against these databases; if the signature is not trusted or is revoked, the boot process halts. Application allowlisting (e.g., Windows Defender Application Control or AppLocker) enforces a policy that only executables with a specific publisher, hash, or path are allowed to run, blocking all unapproved software at runtime.

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 developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SY0-701 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Security Architecture — This question tests Security Architecture — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Enable Secure Boot in firmware. — Secure Boot is a UEFI firmware feature that verifies the digital signature of the bootloader against a database of trusted signatures stored in the firmware. By enabling Secure Boot, the system will refuse to boot from any external media (e.g., USB drives) that does not have a valid, trusted signature, directly preventing unauthorized boot code from executing.

What should I do if I get this SY0-701 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on SY0-701

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A help desk team wants users to be unable to install unsanctioned browser extensions or freeware on corporate Windows laptops, while approved business apps still run. Which endpoint control is best?

easy
  • A.Full-disk encryption on every laptop.
  • B.Application allowlisting or application control.
  • C.A remote access VPN.
  • D.A desktop wallpaper policy.

Why B: Application allowlisting (or application control) is the correct endpoint control because it explicitly defines which software executables, scripts, and installers are permitted to run on the system. By default, all unapproved applications—including unsanctioned browser extensions and freeware—are blocked, while approved business apps are allowed to execute. This directly addresses the requirement to prevent unauthorized installations while maintaining normal operations for sanctioned software.

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

This SY0-701 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 SY0-701 exam.