Examkin

All practice questions

423 questions

All types3,551Multiple choice1,809Multiple select786Numeric12Matching521Ordering423
Question 161Question →

A technician needs to perform a thorough file system repair and bad sector scan on a workstation's primary system volume (C:C:). Because the volume is actively used by the Windows operating system, the repair operation must be scheduled for the next boot cycle. Place the administrative command-line actions in the correct sequential order to schedule and execute this operation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by launching an elevated Command Prompt, issuing the `chkdsk C: /f /r` command, confirming the prompt to schedule the scan on the next reboot by typing 'Y', and restarting the workstation immediately using `shutdown /r /t 0`.
The procedure requires elevated administrative context first because disk repair affects core storage structures. Executing `chkdsk C: /f /r` requests a full repair, but because Windows is actively running from drive C:C:, the utility cannot dismount the volume. Accepting the prompt ('Y') schedules the scan for startup, and calling `shutdown /r /t 0` restarts the system immediately to launch the check.

Step-by-Step Solution

1
Launch elevated Command Prompt
Command Prompt opens with Administrator privileges in `C:\Windows\System32`.
Disk checking utilities require full administrative permissions to access raw storage structures.
2
Issue CHKDSK command with repair switches
The utility detects that drive C:C: is currently in use and cannot be locked.
The `/f` switch fixes errors on the disk, while `/r` locates bad sectors and recovers readable information (implicitly including `/f`).
3
Confirm boot-time scheduling
Windows queues the Autochk utility to execute during the early boot phase.
Since the active OS drive cannot be dismounted online, the check must run before system files are locked by Windows startup.
4
Restart the system immediately
The computer reboots without delay and commences the disk check.
The `shutdown` command with `/r` (reboot) and `/t 0` (zero-second delay) forces an immediate restart to execute the scheduled task.

Key Concept

Scheduling boot-time CHKDSK scans on locked system volumes
Estimated Time:1m 30s
Question 162Question →

A desktop support technician is hardening a standalone Windows 11 Pro workstation to comply with corporate administrative policies. The requirement dictates that administrative users must be forced to enter their password on an isolated desktop whenever an elevation prompt occurs. Place the configuration steps in the correct order to implement and enforce this security baseline.

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, modifying the administrator elevation prompt behavior setting to require credentials on the secure desktop, and finally executing gpupdate /force in an elevated shell to enforce the change immediately.
To properly configure and enforce administrative elevation prompt behavior, a technician must first open secpol.msc, navigate to Local Policies -> Security Options, locate and set 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' to 'Prompt for credentials on the secure desktop', and complete the procedure by running 'gpupdate /force' in an elevated command line.

Step-by-Step Solution

1
Launch the Local Security Policy console using secpol.msc.
The Local Security Policy management interface opens.
Granular UAC elevation behaviors must be configured through secpol.msc on non-domain Windows workstations.
2
Navigate through Local Policies to the Security Options container.
The right pane populates with detailed security parameters and UAC policy options.
UAC security policies are located within the Security Options node.
3
Configure 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' to 'Prompt for credentials on the secure desktop'.
The local policy setting is updated to require password re-entry on the secure desktop for administrative actions.
This specific setting satisfies the mandate requiring re-authentication instead of standard consent.
4
Execute gpupdate /force in an administrative command prompt.
The system re-evaluates local group policies and updates security settings instantly.
Forcing a policy update applies the security changes immediately across the workstation.

Key Concept

Local Security Policy (secpol.msc) UAC Elevation Prompt Configuration
Question 163Question →

A IT support technician is tasked with resolving a malware infection reported on a corporate Windows workstation. Place the following steps of the standard CompTIA 7-step malware remediation process 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 is: 1. Disconnect network cables and isolate the infected workstation from the local network, 2. Disable Windows System Restore to prevent infected restore points from persisting, 3. Update anti-malware signatures and perform a full system remediation scan, 4. Re-enable System Restore and generate a clean restore point, 5. Provide security awareness training and education to the end user.
The CompTIA standard 7-step malware removal process follows a specific order: 1. Identify symptoms, 2. Quarantine infected system, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware and scan/remove), 5. Schedule scans and run updates, 6. Enable System Restore and create restore point, and 7. Educate the user. Isolating the system first stops infection spread, disabling System Restore prevents malware persistence in backup copies, updating and scanning cleans the system, re-enabling System Restore creates a known-good recovery baseline, and user education concludes the process.

Step-by-Step Solution

1
Isolate the system (Quarantine)
Network cables are removed and wireless connections are disabled to prevent lateral malware movement.
Quarantine comes right after identifying malware symptoms.
2
Disable System Restore
Existing restore points containing infected copies of system files are purged.
Prevents accidental restoration of malware from an older system state.
3
Remediate the infection
Anti-malware definitions are updated and scans purge malicious software.
Threats must be remediated using verified, updated tools.
4
Re-enable System Restore
A fresh, clean system restore baseline is created.
Ensures future recovery points are established from a verified uninfected state.
5
Educate the user
The user is trained on safe browsing habits and phishing identification.
User training completes the remediation workflow.

Key Concept

CompTIA 7-Step Malware Remediation Best Practices
Question 164Question →

A cybersecurity technician is responding to a confirmed Trojan infection on an enterprise Windows 11 workstation. Place the following remediation actions in the exact sequential order required by the CompTIA 7-step malware removal process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the CompTIA 7-step malware removal process: 1) Disconnect network interfaces (Quarantine), 2) Disable System Protection (Disable System Restore), 3) Update definitions and run scans (Remediate), 4) Re-enable System Protection and create a restore point (Enable System Restore), and 5) Conduct user awareness training (Educate End User).
The standard CompTIA 7-step malware removal framework mandates the following exact operational sequence: 1. Identify malware symptoms, 2. Quarantine infected systems, 3. Disable System Restore (in Windows), 4. Remediate infected systems (update signatures and scan/remove), 5. Schedule scans and run updates, 6. Enable System Restore and create a restore point, 7. Educate the end user. Disconnecting network adapters isolates the endpoint (Step 2). Disabling System Protection purges malicious restore snapshots (Step 3). Updating definitions and scanning remediates the infection (Step 4). Re-enabling System Protection and generating a restore point establishes a clean baseline (Step 6). Educating the end user completes the process (Step 7).

Step-by-Step Solution

1
Isolate the compromised computer from the local network.
Network communication is halted, preventing malware spreading or command-and-control communication.
This corresponds to Step 2 (Quarantine infected systems) of the CompTIA process.
2
Turn off System Protection in Windows control utilities.
Infected backup snapshots stored in System Restore are deleted.
This corresponds to Step 3 (Disable System Restore) of the CompTIA process.
3
Download current signatures and launch anti-malware scanning engines.
Malicious files, registry keys, and rootkit components are identified and removed.
This corresponds to Step 4 (Remediate infected systems) of the CompTIA process.
4
Turn System Protection back on and initiate a fresh system checkpoint.
A clean backup state is recorded for future administrative recovery.
This corresponds to Step 6 (Enable System Restore and create a restore point) of the CompTIA process.
5
Engage with the end user to review security protocols.
The user gains awareness regarding vector prevention techniques.
This corresponds to Step 7 (Educate the end user) of the CompTIA process.

Key Concept

CompTIA 7-step Malware Removal Best Practices
Question 165Question →

A systems administrator needs to configure standalone Windows 11 Pro workstations so that standard users are automatically denied elevation requests without being prompted for administrator credentials. In what sequential order should the administrator perform the steps to enforce this restriction using the Local Security Policy snap-in?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The administrator must first launch Local Security Policy (secpol.msc), navigate to Security Settings > Local Policies > Security Options, double-click 'User Account Control: Behavior of the elevation prompt for standard users', set the policy value to 'Automatically deny elevation requests', and apply the changes.
Configuring UAC elevation behavior for standard users via Local Security Policy requires launching secpol.msc, navigating to Security Settings > Local Policies > Security Options, opening the policy 'User Account Control: Behavior of the elevation prompt for standard users', setting the option to 'Automatically deny elevation requests', and saving the configuration.

Step-by-Step Solution

1
Launch the management console
Local Security Policy console opens
Administrative policy changes require elevated access through the secpol.msc tool on local machines.
2
Navigate to the Security Options branch
Policy list for UAC and local account controls is displayed
UAC behavior policies are stored under Local Policies > Security Options.
3
Open policy properties for standard user elevation
Policy configuration property window opens
Allows modification of prompt behavior specific to non-administrative accounts.
4
Modify the elevation drop-down selection
Policy is configured to automatically deny elevation
Changing from the default credential prompt to automatic denial prevents credential sharing or prompt spamming.
5
Apply and close policy settings
Changes take effect on the local security baseline
Saves the configuration to enforcement.

Key Concept

User Account Control Local Security Policy configuration for standard user elevation prompts
Question 166Question →

A technician is performing basic workstation hardening on a newly installed Windows computer. Place the following security steps in the logical order they should be performed to secure the system from initial deployment to final user handoff.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with securing default accounts and credentials, followed by updating the system and turning on host firewall protection, then disabling unnecessary services and autorun features to minimize attack surface, and finally configuring screen lock timeouts for end-user environment security.
Securing default user accounts is the foundational step when hardening a system, followed by protecting network access through OS patches and local firewall activation. After establishing base network defenses, unnecessary software services and autorun functions are disabled to shrink the attack surface. End-user security controls, such as screen lock timeouts, are applied last before system deployment.

Step-by-Step Solution

1
Secure account access
Default credentials and Guest accounts are disabled or modified.
Prevents unauthorized initial access via well-known default settings.
2
Apply baseline security updates and firewall controls
Known security patches are applied and incoming traffic is limited.
Secures the network boundary of the host against exploit attempts.
3
Reduce system attack surface
Unused services, open ports, and autorun functions are disabled.
Limits exposure to malicious code execution and background service vulnerabilities.
4
Apply screen lock and password policies
Screen saver timeout and password lock enforce physical security.
Ensures unattended workstations lock automatically when left unattended.

Key Concept

Workstation Hardening Standard Operating Procedure
Question 167Question →

A technician is troubleshooting a desktop workstation that experiences a No POST condition where internal fans spin continuously but no diagnostic beep codes or display output occur. Place the technician's troubleshooting steps in the correct order from first action to last action to systematically isolate the root cause.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct systematic ordering of troubleshooting steps is: 1) Verify power supply unit (PSU) voltage outputs using a multimeter or dedicated tester; 2) Disconnect non-essential peripherals, storage drives, and expansion cards to create a minimal boot configuration; 3) Reset the motherboard CMOS/NVRAM settings using the jumper pin or coin-cell battery removal; 4) Remove the motherboard from the chassis and perform a bench test on a non-conductive anti-static mat.
Systematic hardware diagnostics move logically from non-invasive, quick checks to complex disassembly. First, power supply stability must be verified using a hardware tester to ensure all main motherboard rails receive proper power. Second, establishing a minimal boot configuration (motherboard, CPU, one RAM stick, PSU) isolates faulty add-in cards or storage drives. Third, clearing CMOS clears invalid hardware settings that prevent POST. Finally, removing the motherboard for a bench test checks for grounding shorts against the computer case.

Step-by-Step Solution

1
Test Power Supply Outputs
Confirms the PSU delivers proper +12 V+12\text{ V}, +5 V+5\text{ V}, and +3.3 V+3.3\text{ V} rail power along with the Power Good signal.
Before disassembling internal hardware, verifying clean power delivery ensures component isolation tests yield accurate results.
2
Isolate Minimal Boot Components
Reduces hardware complexity strictly to the power supply, motherboard, CPU, and a single RAM module.
Helps determine if external accessories, storage drives, or secondary add-in cards are overloading or shorting the system.
3
Clear Motherboard CMOS
Restores BIOS/UEFI default settings.
Eliminates corrupted system configuration parameters, invalid memory frequency profiles, or improper CPU multipliers as the source of the POST failure.
4
Breadboard System Outside Chassis
Tests motherboard and core component boot functionality in an open-air environment.
Identifies electrical shorts caused by misplaced motherboard chassis standoffs or grounded rear metal shielding.

Key Concept

CompTIA Hardware Isolation and Troubleshooting Methodology
Question 168Question →

An IT technician is tasked with disposing of retired magnetic backup tapes containing confidential enterprise data according to organizational security policy. Place the steps of the data sanitization and chain-of-custody process 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 magnetic backup tape disposal is: 1) Log the serial numbers in the inventory tracking system, 2) Expose the magnetic tapes to an industrial degausser, 3) Place the degaussed tapes into a locked, tamper-evident container for transport, and 4) Obtain and archive a signed Certificate of Destruction.
Establishing a secure data disposal workflow requires serial number logging first to record asset custody. Next, degaussing purges the magnetic tape data on-site. Securing the media in locked containers preserves physical security during vendor transport. Finally, once physical shredding occurs, receiving the Certificate of Destruction completes regulatory compliance reporting.

Step-by-Step Solution

1
Inventory and document media
Record unique tape serial numbers in the decommission log.
Comprehensive logging ensures full accountability and establishes an unbroken chain of custody before handling begins.
2
Perform initial logical data purging
Degauss the magnetic tapes on-site.
Degaussing disrupts the magnetic fields on magnetic tapes, erasing data on-site so unencrypted information is never exposed during transit.
3
Secure media for transport
Seal degaussed media in locked, tamper-evident transfer containers.
Physical security controls during transport prevent loss, theft, or unauthorized access while en route to shredding.
4
Verify and archive completion documentation
Receive and log the vendor-issued Certificate of Destruction.
The signed Certificate of Destruction serves as compliance proof that media lifecycle management requirements were satisfied.

Key Concept

Data Sanitization and Chain-of-Custody Lifecycle
Question 169Question →

A technician is troubleshooting a desktop application that repeatedly crashes upon launch on a Windows workstation. Place the following troubleshooting steps in the correct order from first to last to isolate and resolve the issue according to standard CompTIA methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of troubleshooting steps from first to last is: 1) Interview the user and inspect Event Viewer logs, 2) Formulate a hypothesis of probable cause, 3) Perform a clean boot to test the hypothesis, 4) Reinstall the application and verify functionality, and 5) Record resolution details in the ticketing system.
The correct order strictly follows the six-step CompTIA troubleshooting methodology: 1) Identify the problem (user interview and Event Viewer log review), 2) Establish a theory of probable cause (hypothesizing service or binary corruption), 3) Test the theory (performing a clean boot), 4) Establish a plan of action and verify full system functionality (reinstalling app and testing stability), and 5) Document findings, actions, and outcomes.

Step-by-Step Solution

1
Gather symptom details and examine the Windows Event Viewer Application log.
The technician identifies faulting module details and error codes.
CompTIA troubleshooting methodology starts with identifying the problem and gathering information.
2
Develop a theory regarding the root cause of the crash.
A probable cause hypothesis (e.g., third-party service conflict or file corruption) is established.
Formulating a theory of probable cause directs targeted testing.
3
Execute a clean boot in Windows to test the hypothesis.
Background third-party interference is ruled in or out.
Testing the theory determines the true cause without making irreversible changes.
4
Reinstall software and verify normal application operation.
The application functions properly without crashing.
Remediation and functionality verification confirm the issue is resolved.
5
Document findings, actions, and outcomes in the ticket history.
Knowledge base records are completed.
Final documentation ensures complete administrative closure.

Key Concept

CompTIA A+ Standard Troubleshooting Methodology applied to Windows Application Crashes
Question 170Question →

An IT support technician is processing a user-reported workstation issue following standard operational procedures and service desk guidelines. Arrange the steps of the ticketing workflow 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 the ticketing workflow is: 1) Log the ticket with complete initial details, 2) Categorize the issue and assign priority level, 3) Perform troubleshooting, implement solution, and log remediation steps, 4) Contact the end user to verify full system functionality, and 5) Update documentation and mark the ticket status as closed.
The standard ticket lifecycle follows a structured progression: initial ticket creation and detail logging, triage/categorization and prioritization, technical troubleshooting with root cause logging, user verification, and finally ticket closure with knowledge base/asset updates.

Step-by-Step Solution

1
Identify and record the incident
Initial ticket record created with user and asset info
All support requests must begin with comprehensive initial documentation.
2
Triage, categorize, and prioritize
Ticket is assigned to the correct queue with appropriate SLA priority
Proper categorization ensures routing to the right support group and timeline.
3
Diagnose, resolve, and document root cause
Technical issue is fixed and resolution steps are recorded
Work performed and root cause analysis must be thoroughly documented in resolution fields.
4
Verify functionality with user
User confirms the system is working as expected
Technicians must never close a ticket without user verification.
5
Finalize documentation and close ticket
Knowledge base updated and ticket status set to closed
Official closure and archiving prevents duplicate tickets and enriches IT documentation.

Key Concept

Ticket Lifecycle Management
Question 171Question →

A field technician is troubleshooting a mobile tablet on which a third-party mapping application continually becomes unresponsive during operation. Sequence the following troubleshooting actions in order from least invasive to most invasive.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence from least invasive to most invasive is: 1) Force close the mapping application and restart it, 2) Clear the application cache through the mobile OS settings, 3) Uninstall and reinstall the mapping application, and 4) Perform a full factory reset of the mobile device.
CompTIA troubleshooting methodology requires technicians to start with the least invasive step that can resolve the issue and progress toward more invasive measures. Force stopping the application is immediate and non-destructive. Clearing the application cache deletes temporary files without erasing user settings. Uninstalling and reinstalling the application replaces corrupted application files but resets app-specific data. Performing a factory reset wipes all data and applications from the entire mobile device and is the most invasive action.

Step-by-Step Solution

1
Identify the immediate, non-destructive process step.
Force closing the application halts the hung process in RAM.
This tests whether a temporary memory glitch caused the issue without changing saved data.
2
Identify the step that removes transient temporary data.
Clearing the application cache deletes temporary cached files.
Corrupted temporary files often cause app freezes, and removing them retains app login and user settings.
3
Identify the step that replaces application program files.
Uninstalling and reinstalling the app installs a fresh copy of the application code.
This resolves deeper corruption within app files or settings but requires downloading the app and re-entering credentials.
4
Identify the system-wide last resort step.
Performing a factory reset wipes the entire storage and restores OS default settings.
Because it destroys all local user data across the entire device, a factory reset is reserved for when all app-specific steps fail.

Key Concept

Least-Invasive Mobile Application Troubleshooting Methodology
Question 172Question →

A security administrator is preparing an unhardened, newly provisioned Windows workstation for deployment in a high-security enterprise environment. To minimize attack vectors prior to placing the system on the production network, the administrator must execute a comprehensive series of local configuration and security hardening controls. In what sequence should the technician perform the following workstation hardening steps to ensure proper dependency management and maximum initial security?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct procedural order is: first disable or rename default accounts and provision secured local accounts, second configure local account security policies (lockout and complexity), third disable unnecessary system services and features (AutoRun/AutoPlay), fourth configure Windows Defender Firewall and port restrictions, and fifth enable full-disk encryption (BitLocker) and screen lock policies.
Hardening a new workstation follows a logical defense-in-depth sequence: establishing strict local access control (account renaming/disabling), defining credential policies (lockout/complexity), minimizing software attack surface (disabling services/AutoRun), controlling network exposure (host firewall/ports), and finally applying physical and storage safeguards (BitLocker and screensaver locks).

Step-by-Step Solution

1
Secure local user and administrator accounts
Default administrative pathways and Guest accounts are restricted or renamed, establishing baseline access control.
Before applying system-wide policies, control over account privileges must be established so default credentials cannot bypass configuration.
2
Enforce Local Security Policy baseline rules
Account lockout thresholds and password complexity criteria are activated via secpol.msc.
Establishing policy bounds on accounts protects the system against brute-force attempts during remaining configuration tasks.
3
Reduce attack surface by disabling unneeded services and features
Unused OS services, background apps, and removable media features like AutoPlay/AutoRun are turned off.
Eliminating unnecessary background features mitigates local and media-borne software vulnerabilities.
4
Restrict network boundaries via host firewall settings
Inbound and outbound network rules block unauthorized protocols and ports.
Network filtering ensures that remaining services do not expose unexpected network ports before network connection.
5
Implement data-at-rest and physical session security controls
BitLocker encrypts system drives and password-protected screensavers lock unattended sessions.
Storage encryption and inactivity timeouts complete the hardening baseline to guard against physical loss or unauthorized local access.

Key Concept

Workstation Hardening Procedural Sequence
Question 173Question →

An IT technician needs to configure several newly unboxed Windows 11 Pro workstations with standard corporate Wi-Fi settings, user accounts, and security policies using a provisioning package instead of performing full disk re-imaging. What is the correct sequence of steps to create and apply this provisioning package?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with configuring the deployment settings in Windows Configuration Designer, exporting the resulting .ppkg file to a USB flash drive, powering on the target system to the Out-of-Box Experience (OOBE) screen, and finally inserting the USB flash drive into the target computer to automatically apply the package.
Provisioning packages (.ppkg) created via Windows Configuration Designer allow technicians to rapidly configure new or existing Windows devices without re-imaging. The workflow requires building the package configuration first, exporting the package to removable media (such as a USB drive), booting the target device into OOBE, and plugging in the drive so Windows detects the package automatically.

Step-by-Step Solution

1
Define configuration settings using Windows Configuration Designer.
A deployment project containing corporate Wi-Fi, policy, and application rules is established.
Windows Configuration Designer is the tool used to build provisioning packages for Windows deployment.
2
Export the project as a .ppkg file onto a USB flash drive.
A standalone provisioning package file (.ppkg) is created on removable media.
The target computer requires access to the compiled .ppkg package to process configuration instructions.
3
Boot the target system into the Out-of-Box Experience (OOBE) screen.
The target computer reaches the initial Windows setup environment.
Provisioning packages are designed to be recognized natively by Windows during the initial OOBE stage.
4
Insert the USB flash drive into the target computer while at the OOBE screen.
Windows automatically detects the .ppkg file and applies all custom corporate settings.
During OOBE, Windows scans connected USB drives for .ppkg packages and prompts or executes automated configuration upon detection.

Key Concept

Windows Provisioning Packages (.ppkg)
Estimated Time:1m 30s
Question 174Question →

A desktop technician needs to update Group Policy settings on a Windows workstation and verify that the computer policies have been successfully applied. Place the following steps in the correct order from first to last to complete this task using the Windows Command Prompt.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of actions begins with opening an elevated Command Prompt, followed by running `gpupdate /force` to refresh policy settings, executing `gpresult /r` to view the immediate summary of applied policies, and finally running `gpresult /h policy_report.html` to export the comprehensive HTML report.
To update and verify Group Policy settings, a technician must first open an elevated Command Prompt. Next, `gpupdate /force` is run to apply policy changes immediately. Then, `gpresult /r` is executed to review the applied policies in the console summary. Finally, `gpresult /h` is used to export a detailed HTML report for auditing.

Step-by-Step Solution

1
Launch Command Prompt with elevated administrator rights.
Access to administrator-level command-line system tools is granted.
Modifying system settings and reading computer-level Group Policy objects requires elevated privileges.
2
Execute `gpupdate /force`.
All local and domain policy settings are refreshed immediately.
Forces an immediate update rather than waiting for the standard background refresh interval.
3
Execute `gpresult /r`.
Displays a summary of applied GPOs and security groups directly in the console.
Allows quick interactive verification that newly assigned policies are actively applied.
4
Execute `gpresult /h policy_report.html`.
Creates a structured HTML file containing complete RSoP details.
Provides an exported file artifact for documentation and long-term auditing compliance.

Key Concept

Group Policy Refresh and RSoP Verification Command-Line Workflow
Question 175Question →

An IT technician is dispatched to resolve a point-of-sale (POS) thermal receipt printer issue where printed receipts are faint and partially illegible. Place the following troubleshooting steps in the correct sequence according to standard CompTIA troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows standard CompTIA troubleshooting methodology: 1) Identify the problem by gathering information, 2) Establish a theory of probable cause regarding thermal printhead contamination, 3) Test the theory using diagnostic test prints, 4) Implement the solution by cleaning the printhead and replacing paper, and 5) Verify system functionality and document the outcome.
The correct order strictly follows the standard CompTIA troubleshooting framework: Identify the problem, establish a theory of probable cause, test the theory, implement the corrective action, and verify full functionality while documenting findings.

Step-by-Step Solution

1
Identify the problem
User symptoms and initial device conditions are observed.
Troubleshooting always begins by gathering details from the user and inspecting the hardware setup.
2
Establish a theory of probable cause
A specific hypothesis is established based on thermal printing mechanics.
Determines the most likely failure point (thermal printhead residue or paper quality) before making hardware changes.
3
Test the theory to determine cause
Root cause is confirmed via diagnostic output.
Validates whether printhead contamination is responsible without performing unnecessary component replacements.
4
Establish a plan of action and implement the solution
Physical maintenance is executed safely.
Cleans the thermal heating elements with isopropyl alcohol and installs supported thermal paper stock.
5
Verify full system functionality and document findings
Full operation confirmed and repair details recorded.
Ensures the issue is resolved to the user's satisfaction and logs the maintenance steps for future reference.

Key Concept

CompTIA Troubleshooting Methodology for Thermal Printer Issues
Question 176Question →

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 177Question →

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 178Question →

A desktop support technician needs to manually install and configure a custom line-of-business application for standard domain users on a Windows workstation. What is the correct logical sequence of steps the technician should follow from pre-installation to user validation?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1) Verify operating system architecture compatibility (32-bit vs. 64-bit) and hardware prerequisites, 2) Right-click the application installer executable and select 'Run as administrator', 3) Select the appropriate destination path (Program Files vs. Program Files (x86)) during the setup wizard, 4) Configure NTFS access control list (ACL) permissions on shared data folders in ProgramData, and 5) Log in as a standard user and launch the application to confirm proper operational functionality.
The correct logical order begins with checking system architecture requirements, followed by elevating installer privileges, specifying the target path during installation, configuring folder ACLs post-install for user data access, and concluding with end-user verification.

Step-by-Step Solution

1
Check CPU and OS architecture alongside vendor hardware requirements.
Confirmed whether a 32-bit or 64-bit installer version is required.
Pre-installation checks prevent installer failures caused by executing incompatible binaries.
2
Elevate setup execution via User Account Control.
The installer obtains access rights needed to modify system registries and root directories.
Standard user accounts lack rights to install software across system-wide directories.
3
Select installation directory in setup configuration.
Files are placed in Program Files (64-bit) or Program Files (x86) (32-bit).
Ensures adherence to Windows file system structure guidelines for 32-bit and 64-bit applications.
4
Adjust directory access control lists for application data storage.
Standard users gain read/write permissions for shared local files in C:\ProgramData.
Standard users are blocked from writing to system directories by default unless explicit permission grant rules are applied post-installation.
5
Conduct functional testing under standard user credentials.
Application opens and operates cleanly without requiring ongoing administrative rights.
Testing under the administrator account would mask missing permissions required by end users.

Key Concept

Application Installation and Configuration Workflow
Question 179Question →

A Windows 11 workstation running a CAD application experiences sudden application crashes during heavy render tasks. Event logs indicate recurring crash events involving faulting module ntdll.dll with memory access violation code 0xc0000005. The technician needs to isolate whether the crash is caused by system file corruption, memory pressure, or third-party background interference. In what sequence should the technician perform the following troubleshooting steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper troubleshooting order follows the CompTIA troubleshooting methodology: 1) Review Event Viewer Application logs to gather specific error details; 2) Monitor real-time performance metrics in Task Manager and Resource Monitor while reproducing the issue; 3) Perform a Clean Boot using msconfig to isolate third-party software conflicts; 4) Execute sfc /scannow from an elevated command prompt to repair corrupted system files; 5) Verify resolution in normal boot mode and document the outcome.
The correct sequence adheres strictly to standard CompTIA troubleshooting procedures. The technician starts by gathering crash details from Event Viewer, observes resource metrics during crash reproduction using Task Manager and Resource Monitor, isolates startup items via Clean Boot, repairs system file integrity using SFC, and concludes by verifying and documenting the resolution.

Step-by-Step Solution

1
Gather detailed crash logs using Event Viewer.
Identifies the specific faulting application, faulting module, and exception code.
Always begin troubleshooting by identifying problem symptoms and gathering event details.
2
Monitor system resources using Task Manager and Resource Monitor during task reproduction.
Measures CPU, RAM, and disk performance metrics under load to detect resource exhaustion or leaks.
Empirical monitoring provides direct insight into system state during application execution.
3
Isolate third-party services using System Configuration (msconfig) for a Clean Boot.
Eliminates potential background service and startup program interference.
Isolating variables is necessary before applying destructive fixes or system repairs.
4
Execute system file repair commands (sfc /scannow).
Scans and replaces damaged or corrupted OS files like ntdll.dll from the Windows component store.
Remediates system-level corruption causing memory access exceptions.
5
Verify complete system functionality and document findings.
Confirms the CAD application operates stably without crashing and logs complete resolution steps.
Finalizing the issue requires verification and documentation per administrative best practices.

Key Concept

CompTIA A+ Software Troubleshooting Methodology for Windows Application Crashes
Estimated Time:1m 30s
Question 180Question →

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)
PreviousPage 9 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin