Security

442 questions

Question 261Question

An IT administrator is preparing a security reference guide for mobile devices. Match each mobile security term on the left with its corresponding operational description on the right.

Click a left item, then click its matching right item

Items

Geofencing
Containerization
Sideloading
Remote Wipe

Matches

Show answer & explanation

Answer

Geofencing matches with restricting device access based on physical location boundaries; Containerization matches with separating enterprise data and applications from personal user storage; Sideloading matches with installing applications from third-party sources outside official app stores; Remote Wipe matches with sending a network signal to erase stored data on a missing or stolen device.
Each security term is paired with its precise industry-standard definition: Geofencing enforces location limits, Containerization segregates business assets, Sideloading describes untrusted app installation, and Remote Wipe executes data sanitization commands remotely.

Step-by-Step Solution

1
Identify the definition of Geofencing.
Matches location-based access control.
Geofencing relies on geographic coordinates to enable or restrict device features.
2
Identify the definition of Containerization.
Matches data separation on mobile devices.
Containerization isolates work profile data from personal data, which is essential for BYOD environments.
3
Identify the definition of Sideloading.
Matches non-official app store installations.
Sideloading bypasses standard vendor application stores, posing security risks.
4
Identify the definition of Remote Wipe.
Matches over-the-air device sanitization.
Remote wipe commands clear data to prevent unauthorized access to missing devices.

Key Concept

Mobile Device Security Controls
Estimated Time:1m 0s
Question 262Question

A systems administrator needs to prevent standard users from attempting privilege elevation on a standalone Windows 11 workstation by suppressing elevation prompts entirely. Arrange the steps required to configure this security restriction using the Local Security Policy management console in the correct administrative sequence.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order begins with launching the console using secpol.msc, navigating to Security Options under Local Policies, selecting the policy 'User Account Control: Behavior of the elevation prompt for standard users', and setting its value to 'Automatically deny elevation requests'.
To modify UAC elevation behavior for standard users, an administrator must first open the Local Security Policy console using secpol.msc, navigate to Local Policies > Security Options, locate 'User Account Control: Behavior of the elevation prompt for standard users', and change its setting to 'Automatically deny elevation requests'.

Step-by-Step Solution

1
Launch the management snap-in
The Local Security Policy snap-in (secpol.msc) opens.
Administrative security settings for UAC are configured inside the Local Security Policy console.
2
Navigate to the Security Options container
The list of local security policies and UAC policies is displayed in the right pane.
Local Policies > Security Options contains the granular User Account Control settings.
3
Open the standard user UAC behavior policy
The policy properties window opens.
This specific policy governs the elevation prompt behavior for accounts without administrative privileges.
4
Configure the security setting to automatically deny elevation
The policy setting is applied, blocking privilege elevation attempts for standard users without displaying credential prompts.
Setting the behavior to automatically deny elevation prevents standard users from attempting administrative actions.

Key Concept

Configuring UAC Standard User Elevation Behavior via Local Security Policy (secpol.msc)
Question 263Question

A tier-2 IT support technician is responding to a confirmed ransomware infection on an enterprise Windows workstation. Place the following remediation actions in the correct sequential order according to the standard CompTIA 7-step malware removal process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard CompTIA 7-step malware removal process: 1. Quarantine infected system (disconnect network), 2. Disable System Restore, 3. Remediate infected system (update signatures and scan), 4. Enable System Restore and create restore point, 5. Educate the end user.
The CompTIA 7-step malware removal process follows a strict sequential order: 1. Identify malware symptoms, 2. Quarantine infected systems, 3. Disable System Restore, 4. Remediate infected systems, 5. Schedule scans and run updates, 6. Enable System Restore and create a restore point, and 7. Educate the end user. Disconnecting network interfaces (quarantine) must occur first to contain the infection. Disabling System Restore comes next to prevent malware from remaining in snapshot backups. Remediating with updated tools comes third. Re-enabling System Restore and creating a clean point occurs after remediation. User education is always the final step.

Step-by-Step Solution

1
Isolate the infected host from the network environment.
Network communication is severed, stopping the malware from spreading to other subnet endpoints or connecting to command-and-control servers.
Quarantining the system is Step 2 in the CompTIA methodology.
2
Turn off System Restore / System Protection in Windows.
Existing restore points containing malicious payloads are deleted, preventing accidental re-infection upon restoration.
Disabling System Restore is Step 3 in the CompTIA methodology.
3
Update signature definitions and execute full anti-malware scan in an isolated environment.
Malicious binaries, registry keys, and background tasks are identified and purged.
Remediating the system is Step 4 in the CompTIA methodology.
4
Re-enable System Protection and generate a new restore point.
A known-good baseline state is saved for future recovery options.
Enabling System Restore and creating a restore point is Step 6 in the CompTIA methodology.
5
Provide security awareness education to the endpoint user.
The user understands attack vectors such as phishing links or suspicious attachments.
Educating the end user is Step 7 in the CompTIA methodology.

Key Concept

CompTIA 7-Step Malware Removal Process Sequence
Question 264Question

An IT support technician is troubleshooting a workstation in a corporate office. The user reports that after finding a flash drive in the building parking lot and plugging it into the workstation to identify its owner, the system became sluggish and initiated unauthorized background network connections. Which of the following social engineering threat types best describes this attack vector?

Show answer & explanation

Answer: Baiting

Answer

Baiting is the social engineering tactic where an attacker leaves malware-laden physical media in a public space to exploit human curiosity.
Baiting occurs when an attacker strategically leaves malware-infected physical media (such as a USB flash drive) in a location where potential victims will find it, relying on human curiosity to persuade the victim to connect the media to a system.

Step-by-Step Solution

1
Identify the primary vector used by the attacker.
The attacker left an infected physical flash drive in a public area (parking lot) accessible to company employees.
Classifying the delivery method and human driver reveals the social engineering tactic.
2
Match the observed tactic to standard threat definitions.
Leaving a physical lure to tempt an individual into plugging it into a network computer is defined as baiting.
Baiting leverages victim curiosity or greed by dangling an attractive physical or digital lure.

Key Concept

Social Engineering: Baiting Attack Vector
Question 265Question

A desktop support technician is configuring security settings on Windows 11 Pro workstations in a shared corporate training lab. Company security policy requires that standard user accounts are automatically denied privilege elevation without displaying a User Account Control (UAC) credential prompt. Arrange the steps in the correct order to configure and verify this policy setting.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1. Open the Run dialog, type secpol.msc, and press Enter to launch the Local Security Policy console. 2. In the left navigation pane, expand Security Settings, expand Local Policies, and select Security Options. 3. Locate and double-click 'User Account Control: Behavior of the elevation prompt for standard users'. 4. Change the local security setting value to 'Automatically deny elevation requests' and click OK. 5. Sign out, log in using a standard user account, and attempt an administrative task to verify that elevation is denied without a prompt.
To block standard users from elevating privileges without displaying a UAC credential prompt, a technician must open Local Security Policy (secpol.msc), navigate to Security Settings > Local Policies > Security Options, locate 'User Account Control: Behavior of the elevation prompt for standard users', set it to 'Automatically deny elevation requests', and verify enforcement by attempting an administrative task under a standard user account.

Step-by-Step Solution

1
Launch Local Security Policy console
The secpol.msc MMC snap-in opens.
Administrative security options for standalone Windows workstations are managed through Local Security Policy.
2
Navigate to Security Options
The list of system and UAC security policies is displayed.
UAC elevation behaviors are stored under Security Settings > Local Policies > Security Options.
3
Open the Standard User Elevation Behavior Policy
The properties window for the target policy opens.
This policy specifically controls whether standard users receive a UAC credential prompt or are blocked.
4
Configure the policy to Automatically Deny elevation
Elevation requests from standard accounts will now fail automatically without prompting for credentials.
Selecting 'Automatically deny elevation requests' satisfies the compliance objective.
5
Verify enforcement with a standard user account
Attempted administrative operations fail immediately with an access denied message.
Testing validates that the policy configuration is properly enforced.

Key Concept

Configuring UAC elevation prompt behavior for standard users in Local Security Policy (secpol.msc)
Question 266Question

An IT technician is deploying new Windows workstations for a finance department. To prevent unauthorized or malicious software from automatically executing when employees insert USB flash drives, which of the following workstation hardening best practices should the technician implement?

Show answer & explanation

Answer: Disable the AutoPlay and AutoRun features across all workstations using Group Policy.

Answer

Disabling the AutoPlay and AutoRun features across all workstations using Group Policy.
Disabling AutoPlay and AutoRun ensures that when removable drives are connected, Windows will not automatically run setup files or executable scripts without explicit user intervention, mitigating drive-by media execution attacks.

Step-by-Step Solution

1
Identify the primary security threat in the scenario.
The threat is the automatic execution of untrusted or malicious files when removable media (such as a USB flash drive) is plugged into a system.
Hardening best practices aim to minimize automated execution vectors on end-user systems.
2
Select the policy control that directly prevents automated media execution.
Disabling AutoPlay and AutoRun prevents the operating system from reading autorun.inf files or automatically prompting users to launch executable files upon mounting media.
Enforcing this setting via Group Policy ensures consistent compliance across all workstations.

Key Concept

Workstation Hardening via Disabling AutoPlay/AutoRun
Question 267Question

An IT technician is preparing to decommission several company workstations containing a mix of Solid-State Drives (SSDs) and enterprise Magnetic Hard Disk Drives (HDDs). Company policy requires that all data on the retired drives be rendered completely unrecoverable according to NIST sanitization guidelines before handing the hardware off to a third-party recycler, and that proof of disposition be retained for regulatory compliance. Which of the following steps should the technician take to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Perform an ATA Secure Erase command on the SSDs to purge all flash memory blocks.; Obtain and archive a formal Certificate of Destruction from the recycling vendor detailing drive serial numbers.

Answer

The technician should perform an ATA Secure Erase on the SSDs to purge the flash memory blocks and obtain a formal Certificate of Destruction detailing serial numbers from the recycling vendor.
ATA Secure Erase sends firmware-level commands to reset all storage blocks on solid-state drives, rendering the data completely unrecoverable while keeping hardware compliant with sanitization standards. Additionally, obtaining a Certificate of Destruction provides legal and auditing proof that specific hardware assets were destroyed or sanitized according to established standards.

Step-by-Step Solution

1
Identify media types and select appropriate sanitization methods.
Recognize that SSDs require logical purging methods like ATA Secure Erase or physical shredding, whereas magnetic media can be degaussed or shredded.
Degaussing is ineffective on flash memory storage (SSDs).
2
Execute drive sanitization commands.
Run ATA Secure Erase directly through drive firmware commands to reset flash blocks.
Standard OS formatting leaves data recoverable, whereas firmware-level ATA commands ensure complete data erasure.
3
Obtain compliance documentation.
Collect a signed Certificate of Destruction from the disposal vendor listing all drive serial numbers.
Retaining official audit logs fulfills corporate policy and regulatory compliance requirements.

Key Concept

Data Sanitization and Disposal Compliance
Question 268Question

A system administrator is hardening a fleet of standalone Windows 11 desktops used by shift workers in a medical laboratory. The security compliance baseline requires prohibiting automatic execution of files from removable storage media, disabling unused guest access, and preventing unauthorized observers from viewing previously logged-on usernames at the Windows sign-in screen. During audit testing, inserting a USB flash drive still presents a pop-up menu allowing users to open media files, and the sign-in screen continues to display the username of the last technician who logged in. Which of the following policy configurations should the administrator implement to resolve both compliance issues?

Show answer & explanation

Answer: Configure 'Turn off AutoPlay' for all drives in Local Group Policy and enable the Security Setting 'Interactive logon: Do not display last signed-in'.

Answer

Configure 'Turn off AutoPlay' for all drives in Local Group Policy and enable the Security Setting 'Interactive logon: Do not display last signed-in'.
Configuring 'Turn off AutoPlay' for all drives within Group Policy prevents Windows from displaying execution prompts or automatically running content when removable USB media is inserted. Additionally, configuring the Security Setting 'Interactive logon: Do not display last signed-in' under Local Security Policy prevents the operating system from revealing the account name of the last user who logged in, fulfilling both required hardening controls.

Step-by-Step Solution

1
Identify the mechanism controlling removable media execution prompts.
AutoPlay handles interactive media prompts and hardware action choices when USB drives are attached.
Setting 'Turn off AutoPlay' for all drives under Computer Configuration > Administrative Templates > Windows Components > AutoPlay Policies prevents interactive media prompts.
2
Identify the Local Security Policy controlling sign-in screen username exposure.
The policy 'Interactive logon: Do not display last signed-in' located under Local Policies > Security Options hides the previously logged-in username.
This mitigates shoulder surfing and username harvesting threats on shared shift-work workstations.

Key Concept

Workstation Hardening Policies (AutoPlay and Interactive Logon Security)
Estimated Time:2m 0s
Question 269Question

An IT security technician is decommissioning a magnetic Hard Disk Drive (HDD) that stored highly sensitive enterprise financial data. To maintain compliance and follow industry best practices, the technician must execute a complete sanitization, destruction, and chain-of-custody lifecycle protocol. What is the correct sequence of steps the technician should take from initial decommissioning to final verification?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence begins with establishing chain-of-custody documentation, followed by logical purging (ATA Secure Erase), physical demagnetization (degaussing), mechanical destruction (shredding), and concluding with obtaining a Certificate of Destruction.
The complete asset disposal lifecycle requires establishing chain of custody first to track media accountability, followed by logical purging (ATA Secure Erase) to protect data in transit. Magnetic sanitization (degaussing) and physical destruction (shredding) ensure irreversible destruction. Finally, auditing and archiving a formal Certificate of Destruction closes the compliance loop.

Step-by-Step Solution

1
Establish initial accountability and tracking.
Drive serial number is logged into the chain-of-custody tracking software.
Tracking prevents unauthorized movement or loss of sensitive media prior to sanitization.
2
Execute logical data sanitization.
Drive data is purged using an ATA Secure Erase operation while still attached to storage hardware.
Purging media prior to physical removal mitigates risk if media is intercepted before physical destruction.
3
Apply magnetic sanitization.
Drive platters are exposed to a degausser, rendering magnetic tracks unreadable and drive electronics non-functional.
Degaussing destroys magnetic domains on spinning platters, preventing data recovery.
4
Perform physical destruction.
The degaussed drive is physically shredded into small fragments.
Physical destruction guarantees complete physical impossibility of media reconstruction.
5
Finalize compliance and auditing logs.
A Certificate of Destruction is received, verified against serial numbers, and archived.
Provides legal and regulatory proof that sensitive data was handled according to compliance standards.

Key Concept

Chain of Custody and Secure Data Disposition Lifecycle for Magnetic Media
Question 270Question

An enterprise administrator is deploying security policies for a fleet of mobile devices used by field technicians accessing sensitive customer data. The organization requires that all corporate emails, internal documents, and proprietary tools operate within an encrypted, isolated workspace that prevents copy-paste capabilities into personal applications. Furthermore, IT must be able to perform a targeted removal of only enterprise data when an employee leaves the company, without affecting personal photos or personal applications. Which of the following controls should the administrator implement to satisfy these requirements?

Show answer & explanation

Answer: Containerization combined with Mobile Application Management (MAM) policies

Answer

Containerization combined with Mobile Application Management (MAM) policies is the correct control.
Containerization creates a secure, encrypted sandbox on the mobile device that isolates corporate applications and data from personal applications. Combined with Mobile Application Management (MAM), administrators can enforce Data Loss Prevention (DLP) rules such as restricting copy-paste actions between enterprise and personal apps, and perform a selective wipe to remove only corporate credentials and data when an employee leaves.

Step-by-Step Solution

1
Analyze the technical requirements in the scenario.
Identified key requirements: isolated/encrypted workspace, prevention of copy-paste between corporate and personal apps, and selective wiping of business data only.
Understanding the precise operational constraints is essential for selecting the appropriate Mobile Device Management security control.
2
Evaluate technologies that enforce data isolation and selective data destruction.
Containerization creates a sandboxed storage boundary separating enterprise apps from personal apps, enforcing clipboard isolation. Mobile Application Management (MAM) enables selective remote wipe capabilities.
Containerization and MAM directly fulfill both data separation and targeted wipe requirements.
3
Eliminate options that misapply full-device controls or network/physical security features.
Full-device encryption and full remote wiping destroy all device data rather than performing a selective wipe. Geofencing and wireless authentication address location boundaries and network security rather than app-level sandboxing.
Alternative choices fail to address the application sandboxing and selective wipe constraints.

Key Concept

Mobile Containerization and MAM (Selective Wipe)
Question 271Question

An organization allows employees to use personal smartphones for work under a Bring Your Own Device (BYOD) policy. The IT department needs the ability to erase corporate emails and sensitive company documents from a device if an employee leaves the company, while leaving the employee's personal data untouched. Which of the following features or security controls best achieves this capability?

Show answer & explanation

Answer: Containerization with selective wipe

Answer

Containerization with selective wipe
Containerization segregates corporate applications and data into a isolated, encrypted sandbox managed by Mobile Device Management (MDM). If an employee leaves the company or a device is decommissioned from BYOD use, administrators can perform a selective wipe, which deletes only the corporate container while leaving personal photos, text messages, and personal applications untouched.

Step-by-Step Solution

1
Identify the operational requirement
The requirement calls for removing company data from a personal device without disturbing the user's personal files.
BYOD policies require protecting enterprise data while maintaining employee privacy.
2
Evaluate mobile device management (MDM) features
Containerization isolates corporate applications and stored data into a dedicated, encrypted virtual boundary.
Separating business and personal data allows granular administrative control.
3
Determine the appropriate wipe procedure
A selective wipe targets only the corporate container, preserving all personal photos, apps, and settings.
Selective wipe satisfies both security and privacy constraints.

Key Concept

Mobile device containerization and selective wipe in BYOD deployment models
Question 272Question

A desktop support technician is tasked with modifying the User Account Control (UAC) behavior for administrators on a newly deployed workstation running Windows 11 Home. The technician attempts to open the Local Security Policy console by running secpol.msc in the Run dialog box, but Windows displays a snap-in initialization error stating that the file cannot be found. Which of the following explains why the technician cannot access this security management tool?

Show answer & explanation

Answer: Local Security Policy (secpol.msc) is not included in the Home edition of Windows and requires Windows Pro or Enterprise.

Answer

Local Security Policy (secpol.msc) is an advanced administrative feature that is excluded from Windows Home editions, requiring a Windows Pro or Enterprise edition to be accessed.
Microsoft limits advanced management utilities like Local Security Policy (secpol.msc) and Local Group Policy Editor (gpedit.msc) to Windows Professional, Enterprise, and Education editions. Attempting to run secpol.msc on a Windows Home edition results in an error because the component binaries and management policies are not installed on that edition.

Step-by-Step Solution

1
Identify the administrative tool requested
The requested tool is secpol.msc (Local Security Policy).
Secpol.msc is used to configure security options, account policies, and User Account Control (UAC) enforcement rules.
2
Evaluate edition feature constraints for Windows 11 Home
Windows Home editions intentionally exclude Local Security Policy (secpol.msc) and Group Policy Editor (gpedit.msc).
Microsoft reserves advanced security management tools and domain management capabilities for business and enterprise editions (Pro, Enterprise, Education).
3
Determine the necessary resolution
Upgrade the workstation to Windows 11 Pro or Enterprise to gain access to secpol.msc.
Features absent due to OS edition limitations cannot be enabled via permissions or standard applets without an edition upgrade.

Key Concept

Windows Edition Feature Differences and Security Policy Management
Estimated Time:1m 0s
Question 273Question

A field systems engineer is servicing a Windows workstation at a remote branch office after local endpoint monitoring software flagged rogue keylogger activity. The engineer has physically disconnected the machine from the network, verified that the host is fully quarantined, and downloaded the latest anti-malware definition signatures onto an isolated USB drive. Which step must the engineer perform NEXT in accordance with standard malware remediation procedures prior to executing the scan and removal process?

Show answer & explanation

Answer: Disable System Restore in Windows.

Answer

Disable System Restore in Windows before running the anti-malware remediation scan.
According to the official CompTIA 7-step malware remediation process, the exact sequence is: 1. Identify malware symptoms, 2. Quarantine infected systems, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware signatures, scan, and remove), 5. Schedule updates and scans, 6. Enable System Restore and create a restore point, 7. Educate the end user. Since the system has already been quarantined and update files obtained, the required next step before performing the remediation scan is to disable System Restore.

Step-by-Step Solution

1
Analyze the completed steps in the CompTIA 7-step malware remediation process.
Step 1 (Identify malware) and Step 2 (Quarantine infected systems) have already been completed.
The scenario states that the keylogger was identified, the host network connection was severed (quarantined), and definition updates were acquired.
2
Determine the mandatory next sequential step before scanning and removing the malware (Step 4).
Step 3 is disabling System Restore in Windows.
Disabling System Restore purges existing restore points and prevents Windows from automatically backing up infected binaries while removal tools are running.
3
Confirm why post-remediation steps must not be performed prematurely.
Scheduling updates (Step 5), creating new restore points (Step 6), and end-user education (Step 7) must occur only after successful remediation.
Performing post-remediation steps prior to scanning leaves active malware payloads in place and jeopardizes system recovery integrity.

Key Concept

CompTIA 7-Step Malware Remediation Process Order
Estimated Time:2m 0s
Question 274Question

A network security administrator is standardizing wireless access controls across corporate headquarters and remote locations. Match each wireless security control or protocol to its primary operational feature.

Click a left item, then click its matching right item

Items

WPA3-Personal
WPA3-Enterprise
802.1X / RADIUS
Captive Portal

Matches

Show answer & explanation

Answer

WPA3-Personal matches Simultaneous Authentication of Equals (SAE); WPA3-Enterprise matches 192-bit cryptographic strength options; 802.1X / RADIUS matches centralized AAA authentication via EAP; Captive Portal matches web traffic interception for guest authentication/AUP acceptance.
Each wireless security mechanism is correctly paired to its underlying protocol or operational behavior: WPA3-Personal uses SAE to defend against offline dictionary attacks; WPA3-Enterprise provides optional 192-bit cryptographic mode; 802.1X/RADIUS supplies centralized AAA authentication using EAP; Captive Portal handles guest traffic redirection and policy acceptance.

Step-by-Step Solution

1
Analyze the personal vs enterprise authentication standards
Identify WPA3-Personal as utilizing SAE and WPA3-Enterprise as offering optional 192-bit cryptographic suites.
SAE provides robust protection against password cracking for shared passphrases, while Enterprise mode focuses on high-grade cryptographic suites.
2
Evaluate enterprise central authentication infrastructure
Associate 802.1X / RADIUS with centralized account management using EAP protocols.
802.1X provides port-based access control authenticating individual domain users against a central RADIUS server.
3
Determine guest access and policy enforcement methods
Link Captive Portal to web redirection for guest user authentication and AUP consent.
Captive portals manage guest access by intercepting HTTP/HTTPS traffic until access conditions are fulfilled.

Key Concept

Wireless Security Protocols and Authentication Frameworks
Question 275Question

An IT security analyst is cataloging recent security incident reports across different departments. Match each security threat scenario to its corresponding social engineering vector or attack classification.

Click a left item, then click its matching right item

Items

Whaling
Piggybacking
Hoax
Logic Bomb

Matches

Show answer & explanation

Answer

Whaling matches the executive-targeted phishing scenario; Piggybacking matches entry into a secured room with employee consent; Hoax matches the false security alert instructing users to delete files; Logic Bomb matches dormant malicious code waiting for a specific trigger condition.
Each attack type matches its defined characteristic operational behavior. Whaling targets top leadership; Piggybacking exploits physical entry courtesy with mutual knowledge; Hoaxes trick personnel using deceptive false warnings; Logic Bombs execute code based on specified temporal or logic triggers.

Step-by-Step Solution

1
Identify digital social engineering targeted by role.
Recognize that targeting C-level executives specifically for financial or corporate data theft is termed Whaling.
Whaling is a specialized sub-category of spear phishing designed to compromise high-value executive targets.
2
Analyze physical security social engineering vectors.
Differentiate Piggybacking (gaining access with consent/courtesy) from Tailgating (gaining access without consent/unnoticed).
Holding a door open intentionally for someone carrying boxes with their consent fits the exact definition of piggybacking.
3
Evaluate social engineering tactics leveraging false panic.
Identify that misleading users into causing self-harm to systems via fake warnings is classified as a Hoax.
Hoaxes exploit fear and urgency to manipulate personnel into deleting files or disrupting operations without using technical exploits.
4
Categorize software threat execution triggers.
Associate dormant code activated by event conditions (like employee status change or specific date) with a Logic Bomb.
Logic bombs execute malicious payloads based on boolean logical triggers built into the codebase.

Key Concept

Classification of Social Engineering and Threat Types
Question 276Question

A security analyst is hardening standalone Windows 11 Pro workstations deployed in a high-security public kiosk environment. The organization requires that whenever a standard user attempts to launch an application or script requiring administrative elevation, Windows must automatically reject the request immediately without displaying a credential prompt. Which Local Security Policy setting under Security Options directly enforces this requirement?

Show answer & explanation

Answer: Set "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests"

Answer

Set "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests"
Configuring 'User Account Control: Behavior of the elevation prompt for standard users' to 'Automatically deny elevation requests' in Local Security Policy directly satisfies the security requirement by automatically blocking standard user privilege escalation attempts without popping up an administrator credential prompt.

Step-by-Step Solution

1
Identify the target user role and requirement
The requirement specifies standard users attempting elevation on Windows 11 workstations, where requests must be automatically denied without prompting.
UAC security policies differentiate between administrators in Admin Approval Mode and standard users.
2
Locate the relevant security policy node in Windows
Open Local Security Policy (secpol.msc) and navigate to Security Settings > Local Policies > Security Options.
Advanced granular UAC behavior settings are managed via Security Options policies rather than standard GUI applets.
3
Select the correct elevation prompt policy for standard users
Configure "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests".
This configuration prevents standard users from elevating privileges or prompting for administrative credentials.

Key Concept

Windows Local Security Policy UAC Elevation Prompt Behavior Settings
Estimated Time:2m 0s
Question 277Question

An IT technician is preparing to harden a newly installed Windows workstation before introducing it into an enterprise environment. Place the following workstation hardening steps in the correct standard procedural sequence, from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for workstation hardening is: 1) Change default credentials and disable unused default accounts, 2) Apply all operating system updates and security patches, 3) Disable unnecessary system services and AutoPlay/AutoRun features, and 4) Enable host-based firewall rules and anti-malware protection.
A baseline workstation hardening workflow follows a logical order: first secure user accounts and default credentials to prevent basic unauthorized access; second, apply system updates and patches to address known security flaws; third, decrease the attack surface by disabling unneeded services and automatic feature execution; and finally, enable host firewalls and anti-malware software for continuous active defense.

Step-by-Step Solution

1
Secure account access
Default credentials are changed and unneeded built-in accounts are disabled.
Prevents unauthorized access using widely known factory default accounts.
2
Patch software vulnerabilities
The operating system is fully updated with security hotfixes.
Closes known system vulnerabilities so update routines work reliably before services are restricted.
3
Reduce system attack surface
Unused services and features like AutoPlay are turned off.
Eliminates superfluous entry points that attackers or automated scripts could exploit.
4
Deploy active defensive security controls
Host firewall rules and anti-malware defenses are active.
Establishes real-time filtering and scanning for ongoing workstation operation.

Key Concept

Standard Workstation Hardening Procedure
Question 278Question

A system administrator needs to sanitize several high-performance NVMe Solid-State Drives (SSDs) containing confidential client data before returning leased server chassis back to the hardware vendor. The lease agreement specifies that all hardware must be returned intact and fully functional. Which of the following methods should the administrator use to render the data irrecoverable while keeping the drives operational?

Show answer & explanation

Answer: Perform an NVMe cryptographic erase or sanitized firmware purge command

Answer

Performing an NVMe cryptographic erase or sanitize command purges all data blocks securely while preserving the drive hardware for lease return.
Performing an NVMe cryptographic erase or firmware sanitize command is the standard purge method for solid-state drives. It permanently destroys data across all NAND cells without causing physical damage, allowing the drives to be reused or returned under lease agreements.

Step-by-Step Solution

1
Identify media type and constraint requirements
Media is flash-based (NVMe SSD), and hardware must remain intact and functional for lease return.
Physical destruction methods (shredding, drilling) cannot be used due to lease return requirements, and degaussing is ineffective on flash storage.
2
Select the appropriate logical sanitization method for solid-state drives
NVMe cryptographic erase or ATA/NVMe Sanitize firmware commands are selected.
Cryptographic erase invalidates encryption keys on self-encrypting drives or sanitizes NAND cells directly, ensuring complete data purge without physical wear or hardware damage.

Key Concept

Selecting media-appropriate sanitization methods based on hardware type and reuse policies
Estimated Time:1m 0s
Question 279Question

An organization is preparing to decommission an enterprise storage array equipped with NVMe Solid-State Drives (SSDs) that held proprietary source code. Security policy requires media sanitization to a Purge standard to allow drive reuse within a lower-security tier. A technician proposes applying a commercial degaussing wand to the drives followed by a standard single-pass zero-fill overwrite. Which of the following technical evaluations best explains why this proposed sanitization plan is flawed?

Show answer & explanation

Answer: Degaussing is ineffective on flash memory storage, and software overwriting cannot reliably target data stored in wear-leveling reserves or bad block pools.

Answer

Degaussing is ineffective on flash memory storage, and software overwriting cannot reliably target data stored in wear-leveling reserves or bad block pools.
The option identifying that degaussing is ineffective on flash memory and that software overwriting cannot reach wear-leveling reserves is correct. SSDs store data using electrical charges in NAND flash cells, which are immune to magnetic degaussing. Furthermore, standard zero-fill overwrite software operates on logical block addresses (LBAs) provided by the OS and cannot sanitize data residing in over-provisioned blocks, retired sectors, or wear-leveling pools managed internally by the SSD controller. Sanitizing SSDs for reuse requires hardware-level commands such as NVMe Sanitize or cryptographic erase.

Step-by-Step Solution

1
Analyze the physical media type specified in the scenario.
The storage devices are NVMe Solid-State Drives (SSDs), which utilize NAND flash semiconductor technology rather than magnetic platters.
Data destruction techniques depend strictly on the underlying physical storage technology.
2
Evaluate the effectiveness of degaussing on solid-state drives.
Degaussing uses high-density magnetic fields to disrupt magnetic domains on HDDs and tapes. Because SSDs store data electronically in floating-gate or charge-trap flash memory cells, degaussing has zero effect on SSD data retention.
Applying magnetic sanitization to non-magnetic media fails to sanitize the data.
3
Evaluate standard software overwriting (zero-fill) on flash storage architectures.
SSDs use wear-leveling algorithms, over-provisioned space, and dynamic block mapping. Standard OS-level zero-fill software only writes to logically exposed sectors and cannot access hidden, wear-leveled, or bad block pools managed internally by the SSD controller.
Achieving a true Purge on SSDs for reuse requires specialized controller commands such as NVMe Sanitize or ATA Secure Erase rather than standard sector overwriting.

Key Concept

Selecting media-appropriate data sanitization and disposal methods for magnetic versus solid-state media.
Question 280Question

A systems administrator is configuring security controls for field technicians who use corporate-issued mobile endpoints to monitor isolated embedded SCADA controllers at remote infrastructure sites. The mobile devices access enterprise cloud resources via cellular networks while concurrently communicating with the embedded IoT devices over local wireless links. Which TWO of the following security configurations should the administrator implement to best protect both the mobile endpoints and the embedded systems?

Select all that apply

Show answer & explanation

Answer: Enforce mobile application management (MAM) containerization to isolate enterprise data from local network interface traffic.; Mandate cryptographically signed firmware verification and disable unneeded physical and wireless ports on the embedded controllers.

Answer

Enforcing MAM containerization on mobile endpoints and mandating cryptographically signed firmware with disabled unneeded ports on embedded controllers.
Mobile application management (MAM) containerization ensures corporate data remains isolated in an encrypted sandbox on mobile devices, protecting sensitive enterprise information when communicating over local short-range links. Simultaneously, embedded IoT devices require attack surface reduction—achieved by shutting down unnecessary physical/wireless ports—and protection against malicious firmware updates via cryptographically signed firmware enforcement.

Step-by-Step Solution

1
Evaluate mobile endpoint data protection requirements when operating across dual networks.
Identified that corporate data must be logically separated from local wireless interfaces accessing embedded hardware.
MAM containerization encapsulates enterprise apps and data in an encrypted volume, preventing data leakage across unauthorized local connections.
2
Evaluate hardening controls required for resource-constrained embedded SCADA/IoT devices.
Identified reducing attack surfaces and preventing unauthorized firmware modifications.
Disabling unused ports eliminates unused entry points, and cryptographically signed firmware prevents malicious code execution.
3
Analyze proposed MDM passcode wipe policies and wireless security protocols for flawed implementations.
Rejected excessive local wipe thresholds and deprecated TKIP encryption settings.
A 3-attempt wipe threshold creates operational disruption, while TKIP is computationally weak and vulnerable to exploitation.

Key Concept

Mobile App Containerization and Embedded System Hardening Controls
Estimated Time:3m 0s
PreviousPage 14 / 23Next
Security Practice Questions — CompTIA A+ (Core 1 & Core 2) — Page 14 | Examkin