Security

442 questions

Question 121Question

A systems administrator at a healthcare facility is investigating a security incident in the radiology department. Several workstations have lost access to local and network files, which now display a .locked file extension alongside a text file demanding cryptocurrency payment within 48 hours. During the initial investigation, the technician learns that an unidentified individual left several unlabeled USB flash drives labeled 'Q3 Executive Bonuses' in the staff lounge, which multiple employees plugged into their workstations. Which of the following threat types and attack vectors are demonstrated in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Ransomware; Baiting

Answer

The threat types demonstrated in this scenario are Ransomware and Baiting.
Ransomware is demonstrated by the unauthorized encryption of user files coupled with a demand for cryptocurrency to restore access. Baiting is demonstrated by leaving malicious USB drives in a common work area with enticing labels to trick employees into introducing malware into the corporate environment.

Step-by-Step Solution

1
Analyze the malicious payload and symptoms described in the scenario.
The renaming of files with a .locked extension and the presence of a cryptocurrency extortion note confirms a file-encrypting malware attack.
Ransomware specifically targets data availability by encrypting files and demanding ransom for decryption.
2
Analyze the social engineering attack vector used to deliver the payload.
Leaving physical USB flash drives labeled enticingly ('Q3 Executive Bonuses') in a common employee area exploits curiosity to compromise systems.
Baiting uses physical media pre-loaded with malware placed strategically to trick users into connecting them to internal network devices.

Key Concept

Social Engineering Vectors (Baiting) and Malware Classifications (Ransomware)
Estimated Time:2m 0s
Question 122Question

A system administrator needs to render confidential data completely unrecoverable on several decommissioned magnetic hard disk drives (HDDs) without physically destroying the drives. Which of the following data sanitization methods should the administrator use?

Show answer & explanation

Answer: Degaussing

Answer

Degaussing is the correct sanitization method for magnetic media when physical destruction is not used.
Degaussing uses a strong magnetic field to disrupt magnetic domains on magnetic drives and tapes, rendering data entirely unrecoverable while leaving the chassis intact.

Step-by-Step Solution

1
Identify the media type and destruction requirements.
The target drives are magnetic HDDs that need full data sanitization without physical destruction.
Different storage media technologies require distinct destruction or sanitization methods.
2
Evaluate data sanitization techniques suited for magnetic storage.
Degaussing disrupts magnetic domains, completely eradicating data stored on magnetic tape and disk platters.
Degaussing permanently neutralizes magnetic alignment without physical shredding or crushing.

Key Concept

Data Destruction and Disposal Methods
Question 123Question

A desktop technician is troubleshooting a legacy 32-bit line-of-business application on a Windows 11 Pro workstation. When a standard user runs the application, configuration changes are saved without issue. However, when an administrative user logs in and opens the application normally (without selecting 'Run as administrator'), the application fails to save changes and throws a permission denied error. An inspection reveals that the application attempts to write settings to C:\Program Files (x86)\LegacyApp\config.ini, where NTFS permissions grant Write access exclusively to the local Administrators group. Which of the following best explains why the application saves configuration changes for the standard user but fails for the administrator?

Show answer & explanation

Answer: User Account Control file virtualization redirects writes to a user-specific VirtualStore directory for standard user tokens, but UAC virtualization is disabled for accounts belonging to the Administrators group.

Answer

User Account Control (UAC) file virtualization intercepts and redirects write attempts to protected system locations like Program Files for standard users into %LOCALAPPDATA%\VirtualStore. However, for administrative accounts operating under Admin Approval Mode, UAC file and registry virtualization is disabled, so direct write attempts to protected directories fail when the application is launched without full administrative privilege elevation.
User Account Control (UAC) includes a legacy compatibility mechanism called file and registry virtualization. When a 32-bit legacy application run by a standard user attempts to write to protected system directories like C:\Program Files (x86), Windows transparently redirects the write operation to %LOCALAPPDATA%\VirtualStore. However, for security and data integrity reasons, UAC virtualization is explicitly disabled for members of the local Administrators group. When an administrator launches the application without elevating ('Run as administrator'), the process runs with a filtered standard user token, but because virtualization is disabled for admin accounts, the direct write attempt to the protected folder is blocked by NTFS permissions.

Step-by-Step Solution

1
Analyze how User Account Control (UAC) handles legacy 32-bit applications writing to protected system directories.
Identify that 32-bit legacy applications writing to C:\Program Files (x86) trigger UAC virtualization for standard users, seamlessly redirecting writes to %LOCALAPPDATA%\VirtualStore.
UAC includes virtualization technology to prevent legacy applications from failing when attempting to write to system-protected file and registry locations.
2
Evaluate the behavior of UAC Admin Approval Mode for accounts in the local Administrators group.
Recognize that UAC disables file and registry virtualization for administrative accounts to prevent split-token inconsistencies.
Administrators are expected to run software with proper elevated privileges rather than relying on VirtualStore redirection.
3
Compare the execution state of the standard user token versus the unelevated administrator token.
The standard user succeeds due to VirtualStore redirection, while the unelevated administrator fails because virtualization is inactive and the token lacks elevated NTFS write rights.
Without explicit privilege elevation ('Run as administrator'), the administrator's filtered token cannot write directly to C:\Program Files (x86), causing the operation to fail.

Key Concept

UAC File and Registry Virtualization Behavior
Question 124Question

A security technician needs to configure a standalone Windows 11 Pro workstation so that standard user accounts are automatically denied elevation requests without displaying a UAC prompt. Place the administrative configuration steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative steps is: 1) Open the Run dialog box, type secpol.msc, and press Enter -> 2) Expand Security Settings > Local Policies and select Security Options -> 3) Double-click User Account Control: Behavior of the elevation prompt for standard users -> 4) Set the local security setting dropdown to Automatically deny elevation requests and click OK.
To enforce auto-denial of elevation requests for standard users on Windows Pro or Enterprise editions, an administrator must launch the Local Security Policy console (secpol.msc), navigate to Security Settings > Local Policies > Security Options, locate 'User Account Control: Behavior of the elevation prompt for standard users', and change its value to 'Automatically deny elevation requests'.

Step-by-Step Solution

1
Launch the Local Security Policy management console using the command secpol.msc.
The Local Security Policy window opens.
Fine-grained UAC behavior rules for distinct account types cannot be set in Control Panel and require the secpol.msc console.
2
Navigate through the policy tree under Security Settings to Local Policies, then select Security Options.
The right pane displays all configurable security option policies.
All administrative User Account Control policies reside within the Security Options folder.
3
Locate and open 'User Account Control: Behavior of the elevation prompt for standard users'.
The policy properties dialog appears.
This specific policy determines whether standard users receive a credential prompt or are blocked directly.
4
Change the security setting to 'Automatically deny elevation requests' and save changes.
Standard users will no longer see UAC prompts when trying to run administrative tasks; requests fail immediately.
Selecting this option fulfills the security requirement to enforce automatic denial without prompt interaction.

Key Concept

Configuring UAC elevation prompt behavior for standard accounts using Local Security Policy (secpol.msc)
Estimated Time:1m 30s
Question 125Question

A network security administrator is deploying a wireless network for an enterprise client's corporate headquarters. The client's security policy strictly requires individual user authentication backed by a centralized RADIUS server, along with modern encryption that eliminates legacy cipher vulnerabilities. Which of the following wireless security configurations should the administrator implement to meet these requirements?

Show answer & explanation

Answer: WPA3-Enterprise utilizing 802.1X authentication with AES encryption

Answer

WPA3-Enterprise utilizing 802.1X authentication with AES encryption
WPA3-Enterprise provides 802.1X framework integration with centralized RADIUS servers for individual credential authentication, while utilizing modern AES-based cipher suites (such as GCMP/CCMP) to secure wireless communications.

Step-by-Step Solution

1
Identify the authentication requirement
Individual user authentication backed by a RADIUS server requires an Enterprise security mode using 802.1X rather than a Personal (Pre-Shared Key / SAE) mode.
Enterprise modes integrate with centralized identity providers (such as RADIUS and Active Directory) to authenticate each user individually.
2
Evaluate the encryption and protocol security requirements
WPA3-Enterprise provides state-of-the-art encryption algorithms (CCMP/GCMP) and eliminates legacy, insecure ciphers such as TKIP.
Legacy ciphers like TKIP are deprecated due to security vulnerabilities, and Personal modes cannot provide per-user authentication logs or individual credential revocation.
3
Select the correct wireless configuration
WPA3-Enterprise with 802.1X authentication meets both the centralized per-user authentication requirement and modern encryption standards.
It combines RADIUS-backed 802.1X EAP authentication with robust modern ciphers.

Key Concept

WPA2/WPA3 Enterprise vs. Personal Authentication and Encryption Standards
Question 126Question

An IT security analyst is investigating a breach where multiple compliance officers' workstations were infected with spyware simultaneously. Email security logs show no suspicious incoming messages, external USB storage devices are blocked via Group Policy, and physical access logs show no unauthorized entry. Analysis reveals that all affected personnel regularly visit a specific third-party industry news website, which had been secretly compromised to serve malicious scripts to site visitors. Which of the following attack types best describes this scenario?

Show answer & explanation

Answer: Watering hole attack

Answer

Watering hole attack
A watering hole attack occurs when an attacker compromises a specific website frequently visited by a target organization or department, planting malware to infect users upon visit. In this scenario, since email logs showed no malicious emails and USB ports were disabled, the infection of multiple users via a frequented third-party news site precisely fits the definition of a watering hole attack.

Step-by-Step Solution

1
Analyze the attack vectors ruled out by the scenario constraints.
Email security logs rule out spear phishing; Group Policy rules out USB baiting; physical access logs rule out physical tampering.
Elimination of vector possibilities based on provided security logs and administrative controls.
2
Identify the common vulnerability exploitation method among all affected users.
All affected workstations visited a compromised third-party industry website frequented by the target department.
Determining the common origin of the malicious payload delivery.
3
Correlate the attack delivery method with CompTIA threat classifications.
Compromising a specific website known to be used by a targeted group to infect their systems is defined as a watering hole attack.
Matching threat behavior to standard security terminology.

Key Concept

Watering Hole Attack Identification
Question 127Question

A helpdesk technician is assisting a user on a Windows 11 Home workstation who attempts to open the Local Security Policy console (secpol.msc) to configure password policy settings. When running the command, Windows displays an error stating that the file cannot be found. Which of the following explains why this management console is unavailable?

Show answer & explanation

Answer: The Local Security Policy snap-in is not included in the Home edition of Windows.

Answer

The Local Security Policy snap-in is not included in the Home edition of Windows.
Microsoft Windows Home editions do not include advanced administrative policy snap-ins such as Local Security Policy (secpol.msc) or Local Group Policy Editor (gpedit.msc). Attempting to launch these MMC snap-ins on a Home edition results in a file not found error because the files are omitted from the installation image.

Step-by-Step Solution

1
Identify the OS edition and requested utility in the scenario.
The workstation is running Windows 11 Home, and the user is attempting to launch Local Security Policy (secpol.msc).
Feature availability in Windows varies across editions.
2
Evaluate feature support for Windows Home versus Pro/Enterprise editions.
Advanced security tools such as secpol.msc, gpedit.msc, and BitLocker are feature-restricted and only available on Windows Pro, Enterprise, and Education editions.
Microsoft excludes domain management and local group policy snap-ins from Home editions by design.
3
Select the option that correctly identifies the Windows edition restriction.
The option explaining that Local Security Policy is not included in the Home edition is correct.
This directly explains why secpol.msc is missing from the operating system.

Key Concept

Windows Edition Security Feature Constraints
Estimated Time:45s
Question 128Question

An IT security technician is designing physical entry security for a high-security server room hosting sensitive financial records. Organization policy mandates implementing measures that actively prevent tailgating (piggybacking) at the doorway, as well as enforcing multi-factor physical authentication that combines a physical security token with a biometric characteristic. Which of the following physical security controls should the technician implement to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Access control vestibule with interlocking doors; Smart card reader paired with a biometric fingerprint scanner

Answer

The correct controls are an access control vestibule with interlocking doors and a smart card reader paired with a biometric fingerprint scanner.
An access control vestibule (mantrap) provides a physical enclosure with interlocking doors that ensures only one person can pass through authentication at a time, directly preventing tailgating. Pairing a smart card reader with a biometric fingerprint scanner enforces multi-factor physical authentication by requiring both a physical possession factor (smart card) and an inherent biological factor (fingerprint).

Step-by-Step Solution

1
Identify the physical security requirement for preventing tailgating at the server room entrance.
Select an access control vestibule (mantrap), which uses a dual-door interlocking mechanism to restrict entry to one person at a time.
Mantraps explicitly block piggybacking/tailgating by preventing the inner door from opening while the outer door is open.
2
Identify the requirement for multi-factor physical authentication.
Select the combination of a smart card badge reader and a biometric fingerprint scanner.
Multi-factor authentication requires combining two distinct authentication factors: something you have (smart card) and something you are (fingerprint biometric).

Key Concept

Physical Access Control and Multi-Factor Physical Authentication
Question 129Question

A systems administrator is configuring local security policies on standalone Windows 11 Pro workstations in a multi-user clinical environment. Management requires that when a workstation is locked or restarted, the sign-in screen must not display the account name or email address of the user who previously logged in. Which setting within Local Security Policy (`secpol.msc`) must the administrator enable to satisfy this requirement?

Show answer & explanation

Answer: Interactive logon: Don't display last signed-in

Answer

Interactive logon: Don't display last signed-in
Enabling 'Interactive logon: Don't display last signed-in' within Local Security Policy (`secpol.msc` under Local Policies > Security Options) ensures Windows will not display the username, full name, or email address of the account that last signed in. This requires any user approaching the workstation to type both their username and password to log in.

Step-by-Step Solution

1
Identify the administrative tool needed for local security configuration.
Open Local Security Policy (`secpol.msc`).
Security policy configurations for local account display and interactive logon are managed within Local Security Policy.
2
Navigate to the Security Options policy container.
Expand Local Policies and select Security Options.
Security Options contains policies governing interactive logon behaviors and User Account Control parameters.
3
Locate and configure the target logon privacy policy.
Enable 'Interactive logon: Don't display last signed-in'.
Enabling this setting ensures that the sign-in screen remains blank until a user explicitly enters their full credentials.

Key Concept

Local Security Policy Interactive Logon Settings
Question 130Question

A system administrator needs to implement WPA3-Enterprise security on an office wireless network to replace an outdated setup. Which TWO of the following authentication components and protocols are required to support a WPA3-Enterprise deployment?

Select all that apply

Show answer & explanation

Answer: Centralized authentication server using RADIUS; IEEE 802.1X framework for network access control

Answer

The required components for WPA3-Enterprise are a centralized RADIUS authentication server and the IEEE 802.1X access control framework.
WPA3-Enterprise requires both an IEEE 802.1X access control framework and a centralized authentication server (such as RADIUS) to authenticate users individually rather than using a single shared passphrase.

Step-by-Step Solution

1
Identify the authentication framework required for enterprise wireless security.
Enterprise modes use IEEE 802.1X to manage network access control and pass authentication packets between client devices and the backend server.
802.1X provides the standard structure for enterprise-grade wireless access control.
2
Determine the server component required for user credential verification.
A RADIUS server is used to maintain and check individual user credentials (or certificates) rather than relying on a shared key.
Centralized credential verification allows individual user account auditing and revocation.

Key Concept

WPA3-Enterprise Security Requirements
Question 131Question

A human resources manager receives an urgent phone call from an individual claiming to be a senior network administrator from the corporate help desk. The caller states that an emergency security patch must be applied immediately to the manager's account to prevent a critical data leak, requiring the manager to read back a one-time passcode sent via SMS and approve an incoming multi-factor authentication (MFA) push notification. After the manager complies, an unauthorized user registers a new authentication device and accesses sensitive personnel records. Which of the following social engineering threat types best describes the attack vector used in this scenario?

Show answer & explanation

Answer: Pretexting

Answer

Pretexting is the correct social engineering attack type described in the scenario.
Pretexting occurs when an attacker invents a scenario (the pretext) and assumes a fraudulent identity—such as a corporate help desk technician—to build trust and trick a targeted employee into granting unauthorized access or revealing sensitive verification codes.

Step-by-Step Solution

1
Analyze the attack vector and communication method presented in the scenario.
The attacker established a fraudulent role (help desk technician) and backstory (emergency security patching) over a voice communication line to manipulate the victim.
Identifying the caller's manipulation tactic helps differentiate between active social interaction vectors and automated/technical attacks.
2
Evaluate the victim's interaction and the resulting compromise.
The victim was duped into disclosing a dynamic multi-factor authentication SMS code and approving an MFA prompt based on the deceptive scenario.
Pretexting relies on creating trust through a realistic narrative (pretext) to convince targets to bypass standard security procedures.
3
Match the observed attack behaviors against CompTIA threat classifications.
Creating an elaborate fake scenario and impersonating authority figures to trick an employee into revealing authentication credentials defines pretexting (specifically vishing/pretexting).
Distinguishing pretexting from passive observation or technical exploitation ensures proper security awareness training and incident reporting.

Key Concept

Social Engineering Principles and Pretexting Identification
Question 132Question

A technician is tasked with removing a malware infection from a workstation. According to the standard CompTIA 7-step malware remediation process, in what sequence should the technician perform the following steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence following the CompTIA 7-step malware removal process is: Quarantine the infected system -> Disable System Restore in Windows -> Remediate the infected system by updating anti-malware software and scanning -> Enable System Restore and create a new restore point -> Educate the end user.
The standard CompTIA 7-step malware removal process follows a specific order: 1. Identify malware symptoms, 2. Quarantine infected system, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware / scan and remove), 5. Schedule updates and run scans, 6. Enable System Restore and create a restore point, 7. Educate the end user. Arranging the actions starting with quarantine and ending with user education strictly aligns with this methodology.

Step-by-Step Solution

1
Isolate the compromised computer from the network.
System is quarantined, preventing malware spread.
Quarantine is step 2 of the remediation framework.
2
Disable System Restore.
Prevents Windows from saving infected files in restore points.
Disabling System Restore is step 3 of the remediation framework.
3
Update signatures and perform malware removal.
Infected files are identified, cleaned, or deleted.
Remediation is step 4 of the remediation framework.
4
Re-enable System Restore and create a clean restore point.
Restores system protection capabilities with clean state.
Enabling System Restore is step 6 of the remediation framework.
5
Provide security awareness guidance to the user.
Reduces future infection risks.
User education is step 7 (the final step) of the remediation framework.

Key Concept

CompTIA 7-step Best Practice Methodology for Malware Remediation
Question 133Question

An IT technician is tasked with decommissioning sensitive magnetic hard drives following standard organizational security procedures. Place the following hardware disposal steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for drive disposal is: 1) Log the hard drive serial numbers in the inventory asset management database, 2) Degauss the magnetic hard drives to neutralize data stored on the platters, 3) Pass the sanitized hard drives through a physical shredder, and 4) Obtain and archive a Certificate of Destruction for regulatory compliance.
The secure decommissioning process begins with administrative logging of serial numbers to maintain audit capability. Magnetic degaussing follows to sanitize data content. Physical shredding then destroys the hardware itself. Finally, obtaining and archiving the Certificate of Destruction validates the completed process for compliance records.

Step-by-Step Solution

1
Identify the initial chain-of-custody administrative requirement.
Documenting serial numbers in the asset database establishes an audit trail before any physical or logical modification.
Tracking must precede destruction so the organization knows which assets are being processed.
2
Perform initial data sanitization on the magnetic media.
Degaussing disrupts the magnetic domains on the platters, sanitizing the stored data.
Sanitizing media prior to physical transport or shredding minimizes data exposure risks.
3
Execute physical destruction of the hardware.
Industrial shredding destroys the physical integrity of the platters and drive electronics.
Physical destruction prevents drive reconstruction.
4
Finalize compliance documentation.
A Certificate of Destruction is generated and logged for legal and regulatory audit purposes.
Final documentation completes the disposal lifecycle and proves compliance.

Key Concept

Chain of Custody and Secure Hardware Disposal Lifecycle
Question 134Question

A network technician is assigned to physically secure desktop computers located in a publicly accessible library area. Recent audits revealed that unauthorized users have been plugging hardware keyloggers into open USB ports on the back of the computer towers. The technician needs to prevent unauthorized physical connections to these ports without replacing the existing computer cases or restricting user access to connected peripherals. Which of the following physical security controls should the technician implement?

Show answer & explanation

Answer: Install physical USB port locks in all empty USB ports.

Answer

Install physical USB port locks in all empty USB ports.
Installing physical USB port locks (or port blockers) directly prevents unauthorized insertion of hardware keyloggers and rogue USB storage devices into empty interface ports on the workstation.

Step-by-Step Solution

1
Identify the physical security threat in the scenario.
The primary threat is unauthorized physical access to open hardware interfaces (USB ports) on computer towers in a public space.
An attacker can insert rogue hardware keyloggers or flash drives into exposed ports to compromise systems.
2
Evaluate the control options against the specific requirement to block port access without altering computer cases.
USB port locks directly block empty USB slots using a specialized key mechanism, effectively disabling physical hardware insertions.
This target-specific control prevents unauthorized device insertion while allowing existing keyboard and mouse connections to function.

Key Concept

Physical USB Port Blockers and Interface Security
Question 135Question

A security technician is configuring group policies for Windows 11 Pro workstations in a finance department. To prevent background malware from interacting with or capturing keystrokes during privilege escalation requests, the technician must enforce a policy that dims the screen and isolates the elevation prompt from the interactive user desktop. Which User Account Control (UAC) security policy setting directly controls this behavior?

Show answer & explanation

Answer: User Account Control: Switch to the secure desktop when prompting for elevation

Answer

The setting 'User Account Control: Switch to the secure desktop when prompting for elevation' is responsible for dimming the screen and displaying elevation requests in an isolated session protected from background software.
Enabling 'User Account Control: Switch to the secure desktop when prompting for elevation' transfers control to a separate desktop context running as SYSTEM. This dims the screen and prevents untrusted user-mode applications or malware from taking screenshots, capturing input, or clicking buttons automatically on the UAC prompt.

Step-by-Step Solution

1
Identify the security requirement described in the scenario
The requirement is to isolate elevation prompts from background processes and malware to prevent keystroke logging or UI spoofing during escalation.
UAC provides a feature called the Secure Desktop, which runs under system privileges and blocks unauthorized process interaction.
2
Evaluate the Local Security Policy settings related to UAC prompt rendering
The policy 'User Account Control: Switch to the secure desktop when prompting for elevation' specifically governs whether the desktop transitions to this protected display mode.
Disabling this policy allows prompts to appear on the standard interactive desktop without screen dimming, increasing vulnerability to malicious background scripts.

Key Concept

Windows UAC Secure Desktop Isolation
Estimated Time:1m 0s
Question 136Question

A desktop technician is reviewing Windows User Account Control (UAC) settings across company workstations. Which TWO of the following statements correctly describe default UAC prompt behaviors for user accounts on Windows systems? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Standard user accounts are required to enter administrator credentials when attempting actions that require elevated rights.; Administrator accounts operating under the default UAC notification level are prompted on the Secure Desktop when programs attempt to make changes.

Answer

Standard user accounts must enter administrative credentials to perform elevated actions, and administrative accounts under default UAC settings receive confirmation prompts on the Secure Desktop when applications request system changes.
Under Windows User Account Control (UAC), standard user accounts are required to provide administrator credentials to elevate privileges. Additionally, accounts in the local Administrators group operate with a split access token by default, meaning software elevation requests trigger a prompt on the dimmed Secure Desktop requiring user confirmation.

Step-by-Step Solution

1
Analyze standard user UAC behavior in Windows.
Standard users lack elevated access tokens; UAC enforces Over-the-Shoulder (OTS) authentication requiring an administrator password.
Prevents unauthorized standard users from making administrative system changes.
2
Analyze administrator account default UAC behavior in Windows.
Administrators log in with a filtered standard user token; UAC prompts on the Secure Desktop (Admin Approval Mode) when software requests full administrative rights.
Prevents unauthorized background scripts or malware from elevating silently without user awareness.

Key Concept

Windows User Account Control (UAC) Account Elevation Behaviors
Question 137Question

A cybersecurity support technician is dispatched to remediate a corporate desktop that is actively displaying unauthorized ransomware warnings and generating rogue outbound connections. In what sequence should the technician perform the following incident response steps to ensure complete malware eradication according to standard CompTIA guidelines?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the CompTIA 7-step malware removal process: (1) Quarantine the system by disconnecting network cables/Wi-Fi, (2) Disable System Restore, (3) Remediate the system by updating signatures and scanning in Safe Mode, (4) Schedule updates and recurring scans, (5) Re-enable System Restore and create a restore point, and (6) Educate the end user.
The CompTIA 7-step malware remediation process specifies an exact operational sequence: 1. Identify symptoms, 2. Quarantine infected system, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware and scan/remove), 5. Schedule updates and recurring scans, 6. Enable System Restore and create restore point, and 7. Educate end user.

Step-by-Step Solution

1
Isolate the workstation (Quarantine)
Network communication is terminated, stopping malware propagation and command-and-control communication.
Step 2 of the CompTIA process dictates quarantining the system immediately after symptom identification.
2
Disable System Restore
System Restore points are cleared, eliminating stored copies of the malware.
Step 3 prevents infected files from being cached or restored later.
3
Remediate the system
Anti-malware definitions are updated and malicious files/registry keys are detected and removed.
Step 4 involves updating security tools and running deep scans to clean the operating system.
4
Schedule updates and scans
Automated security maintenance tasks are established.
Step 5 ensures ongoing preventative maintenance.
5
Enable System Restore and create a clean restore point
System recovery capabilities are restored using a known-clean baseline state.
Step 6 re-establishes OS backup functionality only after confirming system health.
6
Educate the user
The end user learns risk mitigation techniques to avoid future infections.
Step 7 finishes the remediation lifecycle by addressing human vulnerabilities.

Key Concept

CompTIA 7-Step Best-Practice Malware Removal Process
Question 138Question

An IT administrator is configuring a high-security corporate wireless network for a firm's mobile workforce. Corporate policy mandates mutual authentication using client and server digital certificates integrated with a central RADIUS server. Additionally, legacy non-domain mobile devices that only support shared passphrases must be accommodated on a segregated network segment using current security standards. Which TWO of the following configuration choices must the administrator implement to satisfy all policy requirements?

Select all that apply

Show answer & explanation

Answer: Configure WPA3-Enterprise utilizing EAP-TLS authentication for the corporate wireless network; Deploy a dedicated SSID for legacy devices utilizing WPA3-Personal with Simultaneous Authentication of Equals (SAE) assigned to an isolated VLAN

Answer

The administrator must implement WPA3-Enterprise utilizing EAP-TLS authentication for corporate clients, and deploy a dedicated SSID using WPA3-Personal (SAE) on an isolated VLAN for non-domain passphrase devices.
WPA3-Enterprise configured with EAP-TLS satisfies the mutual certificate authentication requirement because EAP-TLS explicitly requires both server-side and client-side digital certificates. WPA3-Personal with SAE on an isolated VLAN provides modern passphrase security and logical traffic separation for non-domain devices without resorting to deprecated encryption algorithms.

Step-by-Step Solution

1
Evaluate enterprise authentication protocols against the requirement for mutual certificate authentication.
Select EAP-TLS under WPA3-Enterprise.
EAP-TLS is the standard EAP type that mandates digital certificates on both the RADIUS server and the client machine for mutual authentication.
2
Evaluate options for passphrase-based clients needing network isolation.
Select WPA3-Personal (SAE) on a separate VLAN.
SAE provides strong key exchange for passphrase-authenticated clients while VLAN isolation ensures non-domain devices remain segregated from corporate assets without relying on weak legacy ciphers like TKIP.

Key Concept

Wireless Security Protocols and Enterprise Authentication Mechanisms
Estimated Time:2m 0s
Question 139Question

A security administrator needs to harden a standalone Windows 11 Enterprise computer by ensuring that only digitally signed executables can request privilege elevation, while requiring administrators to re-enter credentials on a dimmed, isolated desktop. Place the administrative configuration and verification steps in the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with launching secpol.msc, navigating to Security Options under Local Policies, enabling the policy to only elevate signed and validated executables, configuring administrator prompt behavior to require credentials on the secure desktop, and finally testing the policy by executing an unsigned application.
The correct procedural order requires launching the Local Security Policy console (secpol.msc), navigating to Local Policies -> Security Options, enabling digital signature enforcement for elevated binaries, setting administrative prompt behavior to require credentials on the secure desktop, and finally executing a verification test using an unsigned binary.

Step-by-Step Solution

1
Launch the Local Security Policy snap-in console (secpol.msc).
The Local Security Policy window opens.
Administrative security options for UAC cannot be set in standard user applets; secpol.msc must be initialized first.
2
Navigate to Security Settings -> Local Policies -> Security Options.
The list of Windows UAC and security policy settings is displayed.
UAC security policies are located specifically within the Security Options subfolder of Local Policies.
3
Enable 'User Account Control: Only elevate executables that are signed and validated'.
Unsigned applications are prohibited from raising UAC privilege elevation prompts.
This policy forces PKI signature validation prior to granting elevation tokens to executables.
4
Configure 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' to 'Prompt for credentials on the secure desktop'.
Administrators must re-enter password credentials on an isolated secure desktop session during elevation.
The Secure Desktop prevents unprivileged background software on the interactive desktop from intercepting credentials or injecting synthetic click events.
5
Execute an unsigned application binary to confirm enforcement.
The elevation request fails or is refused without presenting an elevation prompt.
Verification confirms that the active security policy blocks unsigned executables in accordance with the security baseline.

Key Concept

Windows Local Security Policy configuration for User Account Control (UAC) code signing enforcement and secure desktop privilege elevation behavior
Estimated Time:2m 0s
Question 140Question

An IT security technician is implementing a hardened security baseline on Windows 11 Pro workstations for a finance company. The compliance policy mandates two specific behaviors: local administrators must be required to explicitly approve administrative privileges on an isolated secure desktop, and standard users must be completely restricted from seeing credential elevation prompts when attempting administrative operations. Which TWO configuration actions in the Local Security Policy snap-in (secpol.msc) under Security Options should be implemented to fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" to "Prompt for consent on the secure desktop".; Configure "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests".

Answer

The correct configurations are setting administrator prompt behavior to prompt for consent on the secure desktop and setting standard user elevation requests to automatically deny.
The combination of prompting for consent on the secure desktop for administrators and automatically denying elevation requests for standard users directly satisfies both audit requirements using Windows Local Security Policy settings.

Step-by-Step Solution

1
Identify the Local Security Policy location
Navigate to Local Policies -> Security Options within secpol.msc on supported Windows Pro/Enterprise editions.
UAC elevation prompt policies are located centrally under Local Security Policy security options.
2
Configure Administrator Prompt Behavior
Set 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' to 'Prompt for consent on the secure desktop'.
This satisfies the requirement for administrators to explicitly approve privilege requests on a secure dimming desktop.
3
Configure Standard User Elevation Policy
Set 'User Account Control: Behavior of the elevation prompt for standard users' to 'Automatically deny elevation requests'.
This satisfies the requirement to suppress credential prompts for standard users, automatically rejecting unauthorized elevation attempts.

Key Concept

Windows User Account Control (UAC) Local Security Policies
PreviousPage 7 / 23Next
Security Practice Questions — CompTIA A+ (Core 1 & Core 2) — Page 7 | Examkin