Examkin

All practice questions

423 questions

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

A system administrator reports that a critical rendering workstation emitted a burning odor, abruptly powered down, and now fails to complete POST with no video output upon power-on attempts. Place the following diagnostic and isolation steps in the correct chronological sequence to safely identify and resolve the root cause according to standard CompTIA hardware troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct diagnostic sequence begins with disconnecting AC power and visually inspecting for physical/thermal damage, testing the power supply unit in isolation, performing an out-of-chassis minimal POST test to eliminate grounding shorts, and finally conducting hardware stress tests under load.
The proper troubleshooting process follows a systematic path from low-risk physical/visual inspection to electrical isolation, core platform minimal testing, and final load verification. Disconnecting AC power and visually checking for burnt components protects hardware and personnel. Testing PSU output ensures stable voltage delivery. Breadboarding removes chassis shorting factors, and final software stress testing ensures long-term operational stability under heavy compute loads.

Step-by-Step Solution

1
Ensure safety and prevent further hardware damage by disconnecting AC power and inspecting physical components.
Identifies immediate physical hazards such as burnt PCB traces or blown capacitors.
CompTIA hardware methodology prioritizes safety and visual inspection before applying electrical current to a damaged system.
2
Isolate the Power Supply Unit (PSU) from the motherboard and test voltage outputs and the PWR_OK signal.
Verifies whether DC rail voltages (+12 V, +5 V, +3.3 V) are within ±5% tolerances.
Prevents damage to replacement or functional system components if the original power supply has experienced internal shorting or voltage regulation failure.
3
Perform a bare-bones out-of-chassis (breadboard) POST test with minimal essential hardware.
Isolates motherboard functionality from chassis short circuits, extra expansion cards, and storage drives.
Determines whether the core platform (motherboard, CPU, single RAM stick) can achieve POST without chassis ground faults or peripheral interference.
4
Reassemble system inside the chassis and run diagnostic stress tests (e.g., MemTest86 and CPU thermal benchmarks).
Validates system stability and thermal dissipation under real-world multi-threaded workloads.
Ensures intermittent heat-induced or load-induced power failure issues are fully resolved before returning the machine to production.

Key Concept

CompTIA Hardware Troubleshooting Sequence for Motherboard, Power, and CPU Component Isolation
Question 2Question →

A high-performance workstation unexpectedly powers down during intensive multi-threaded rendering tasks. Upon immediate restart, the machine fails to POST and outputs a memory initialization failure beep code. However, after resting powered off for 20 minutes, the machine boots normally into the operating system. In what sequence should a technician execute the diagnostic steps to safely isolate the thermal or electrical root cause according to standard CompTIA troubleshooting methodology?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence starts with log review, followed by motherboard visual inspection, PSU voltage and signal testing under load, memory channel isolation via minimal boot configuration, and finally CPU thermal assembly inspection and re-seating.
The correct diagnostic flow adheres strictly to CompTIA troubleshooting guidelines: start with non-intrusive software log gathering, progress to external and physical visual safety checks, verify fundamental power delivery stability, perform component-level isolation (RAM sticks), and finish with invasive sub-assembly teardown (CPU socket inspection).

Step-by-Step Solution

1
Review UEFI and OS logs.
Identifies recorded over-temperature or voltage drop thresholds without physical intervention.
Non-intrusive log analysis captures diagnostic evidence before power cycling or hardware disruption clears transient fault indicators.
2
Perform physical visual inspection of the motherboard.
Checks for bulging capacitors, scorched voltage regulator modules (VRMs), or thermal trace damage.
Visual confirmation of physical motherboard degradation prevents powering on a shorted board.
3
Measure Power Supply Unit (PSU) voltage rails and PWR_OK signal under load.
Verifies +12V, +5V, +3.3V rail tolerances and power-good timing under thermal stress.
Stable power delivery must be confirmed before attributing system failures to individual semiconductor components.
4
Isolate RAM modules using a minimal boot configuration.
Determines if memory failure POST codes stem from a specific DIMM, socket, or thermal memory bus fault.
Testing individual memory sticks isolates thermal expansion defects in RAM without disassembling the cooling system.
5
Disassemble, inspect socket pins, and re-seat the CPU with thermal compound.
Resolves or confirms CPU socket pin expansion problems or thermal paste breakdown causing thermal throttling power-offs.
Most invasive disassembly step reserved for after non-invasive and module-level isolation steps fail to yield a resolution.

Key Concept

CompTIA Systematic Hardware Diagnostic Methodology for Thermal and Power Fault Isolation
Question 3Question →

A Windows 11 workstation fails to boot following a forced shutdown during a cumulative update installation. An IT technician accesses the Command Prompt within the Windows Recovery Environment (WinRE) to remediate corrupted system files and restore normal startup. Order the following administrative command-line steps sequentially to execute a complete offline repair workflow.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with using Diskpart to identify target partition letters, followed by reverting pending update operations via DISM, repairing the offline Component Store from install media, running System File Checker with offline parameters, and finally rebuilding the Boot Configuration Data using Bootrec.
The sequence follows the standard Windows offline servicing protocol: First, Diskpart confirms actual volume assignments in WinRE. Second, DISM reverts pending update states that block file access. Third, DISM restores the offline Component Store using clean installation media. Fourth, SFC scans and replaces corrupted OS files against the validated Component Store using offline path parameters. Fifth, Bootrec rebuilds the Boot Configuration Data to ensure proper boot sequence execution.

Step-by-Step Solution

1
Identify volume mappings in WinRE
Discovered offline Windows OS directory located on drive D:\ and installation ISO mounted on drive E:\.
WinRE assigns drive letters dynamically; verifying directory paths is necessary before executing targeted offline commands.
2
Clear pending update locks
Pending update flags and locked servicing transactions are reverted.
Interrupted updates lock component store binaries, preventing repair tools from modifying damaged system files.
3
Repair offline Component Store (WinSxS)
The local component store image is restored to a healthy state using install.wim as a reference source.
System File Checker relies on a valid component store payload to replace corrupted system binaries.
4
Perform offline System File Checker scan
Corrupted Windows system files on drive D:\ are repaired.
Running SFC offline requires explicit /offbootdir and /offwindir switches pointing to the target Windows OS directory.
5
Rebuild boot loader entries
The Boot Configuration Data (BCD) store is updated to point to the operational OS installation.
Ensures the bootloader recognizes the repaired OS and boots into the desktop successfully.

Key Concept

Offline Windows Recovery Workflow using DISM, SFC, Diskpart, and Bootrec
Question 4Question →

A network technician is troubleshooting a corporate laptop displaying a 'No Internet, Secured' wireless status. Arrange the following diagnostic steps in the standard bottom-up troubleshooting sequence, starting with the physical and data link layers and ending with application layer testing.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with checking the physical Wi-Fi hardware switch, followed by verifying SSID association and security authentication, inspecting IP configuration via ipconfig, and concluding with testing DNS resolution and remote IP connectivity.
Following the standard OSI bottom-up troubleshooting methodology requires confirming physical radio power (Layer 1), wireless SSID/security association (Layer 2), valid DHCP IP configuration (Layer 3), and finally testing DNS and remote IP reachability (Layers 4–7).

Step-by-Step Solution

1
Check physical Wi-Fi switch and network adapter status.
Ensures the radio transceivers are powered and operational.
Troubleshooting should start at Layer 1 to ensure hardware is functional before testing logical configurations.
2
Validate SSID selection and re-enter WPA3 authentication credentials.
Establishes Layer 2 link-layer association with the wireless access point.
If Layer 2 association fails, the client cannot communicate with local network services like DHCP.
3
Run `ipconfig /all` in the command prompt.
Verifies that Layer 3 network parameters (IP address, subnet mask, gateway) are properly assigned.
Identifies issues such as self-assigned APIPA addresses (169.254.x.x169.254.x.x) caused by DHCP unreachable errors.
4
Perform `ping` and `nslookup` diagnostic commands.
Confirms remote gateway reachability and proper host name resolution.
Tests upper-layer protocol services to confirm full internet capability once lower layers are operational.

Key Concept

OSI Bottom-Up Network Troubleshooting Methodology
Question 5Question →

A systems administrator needs to deploy a legacy 32-bit enterprise accounting software package on 64-bit Windows 11 corporate workstations. The application installer requires administrative privileges, stores shared database files in `%ProgramData%`, and must be verified for standard non-administrative domain users. Place the following installation, permission configuration, and verification steps into the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with verifying system requirements and architecture compatibility, followed by executing the elevated installer with unattended switches, modifying NTFS write permissions on the shared ProgramData directory, setting legacy compatibility properties on the executable, and concluding with standard user login and verification.
A proper application deployment follows a structured lifecycle: prerequisites assessment must precede file installation; administrative privileges are used to execute the setup package; post-install configuration (such as modifying ProgramData NTFS permissions and setting compatibility modes) prepares the environment for standard users; and testing under a standard user profile validates least-privilege functionality.

Step-by-Step Solution

1
Assess pre-installation prerequisites and architecture
Confirmed 64-bit Windows 11 OS can run 32-bit software via WoW64 in Program Files (x86).
Before making system changes, administrators must verify OS architecture, available disk space, and application dependencies.
2
Execute installer with administrative elevation and silent parameters
Application files are copied to Program Files (x86) without user interaction.
Standard users lack permission to write to system directories, requiring elevated privileges during installation.
3
Adjust NTFS ACLs on shared application directory in ProgramData
Standard Users group is granted Write/Modify permissions on the shared database path.
Legacy applications often fail when attempting to update database files stored in ProgramData if standard users only have default Read permissions.
4
Apply compatibility settings to the application executable
Executable configured to run under legacy Windows compatibility settings.
Compatibility fixes must be applied directly to the installed application binary prior to end-user launch.
5
Perform end-to-end verification using a standard domain user account
Application launches cleanly without UAC prompts and successfully saves data.
Testing with least-privilege credentials ensures the deployment is successful and operational for standard corporate users.

Key Concept

Application Installation and Configuration Workflow
Question 6Question →

A helpdesk technician needs to adjust the User Account Control (UAC) notification level on a Windows 10 workstation using the standard Control Panel interface. In what sequence should the technician perform the following steps to access and apply the new UAC settings?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to modify UAC settings via the Windows GUI is to launch Control Panel, navigate through User Accounts, open 'Change User Account Control settings', and finally adjust the slider and click OK.
The correct procedural order requires initiating navigation from the Windows Control Panel, selecting User Accounts to find administrative options, choosing 'Change User Account Control settings' to open the slider interface, and adjusting the slider before committing the change with OK.

Step-by-Step Solution

1
Launch the Control Panel application from the Start menu search.
The main Control Panel window opens.
Control Panel hosts the classic User Accounts configuration applets in Windows.
2
Navigate to the User Accounts section.
User account configuration features and options are displayed.
User Account Control settings are grouped under the User Accounts management category.
3
Click the link labeled 'Change User Account Control settings'.
The User Account Control Settings configuration popup displays a vertical four-position slider.
This link directly triggers the elevation prompt notification management window.
4
Set the vertical slider to the target notification level and select OK.
The workstation updates its UAC prompt policy behavior.
Moving the slider selects the threshold for credential/consent prompts, and selecting OK applies the setting.

Key Concept

Windows Security Settings and User Account Control
Question 7Question →

An IT support specialist is responding to a reported malware infection on a company workstation. Arrange the following actions in the correct sequence according to the standard CompTIA malware removal process, starting with the earliest step and ending with the final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the CompTIA 7-step remediation process: 1. Disconnect the infected workstation from the network (Quarantine), 2. Turn off System Restore (Disable System Restore), 3. Update anti-malware definitions and perform a thorough scan (Remediate), 4. Re-enable System Restore and create a clean baseline restore point (Enable System Restore), and 5. Conduct security awareness training (Educate the user).
The standard CompTIA 7-step malware removal workflow mandates the sequence: Identify -> Quarantine -> Disable System Restore -> Remediate (Update & Scan) -> Schedule Updates & Scan -> Enable System Restore & Create Restore Point -> Educate End User. Isolating the system comes first to contain the threat. Disabling System Restore removes corrupted backups. Updating definitions and scanning removes the threat. Re-enabling System Restore creates a verified safe baseline. Finally, user education prevents recurrence.

Step-by-Step Solution

1
Isolate the infected endpoint from the network infrastructure.
The machine is quarantined to prevent lateral movement of the malware.
Quarantining the infected system immediately follows identifying the malware symptoms.
2
Disable the Windows System Restore feature.
All existing restore points (which may contain malware copies) are deleted.
Disabling System Restore prevents malware from preserving itself in restore archives.
3
Update malware signatures and run remediation tools.
The active malware infection is detected and eradicated.
Remediation requires updated signatures and scanning, typically performed in Safe Mode.
4
Turn System Restore back on and create a new restore point.
System Protection is active again with a known-good clean state image.
System Restore should only be re-enabled after verifying the system is completely clean.
5
Provide end-user training on safe computing practices.
The user is educated on recognizing phishing, rogue downloads, and social engineering.
Educating the user is the final step of the malware removal framework.

Key Concept

CompTIA 7-Step Malware Removal Process Order
Question 8Question →

An enterprise systems administrator is decommissioning a high-security server room containing legacy magnetic hard disk drives (HDDs) holding regulated customer financial records. Company policy mandates a strict sanitization and disposal workflow adhering to NIST SP 800-88 guidelines and complete chain-of-custody preservation. Place the technician's disposition actions in the correct chronological order from start to finish.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence begins with recording drive serial numbers and securing them in tamper-evident containers, followed by degaussing the magnetic media, mechanically shredding the drives, inspecting shredded fragments for compliance, and finally obtaining a signed Certificate of Destruction to update inventory records.
Proper security lifecycle management requires maintaining strict chain of custody from beginning to end. Serial numbers must first be logged and packaged securely. Magnetic drives are then degaussed to purge data prior to mechanical destruction. Physical shredding follows degaussing to ensure hardware cannot be reconstructed. The shredded residue is visually verified to meet particle size standards, and finally, a signed Certificate of Destruction is executed to update organizational records.

Step-by-Step Solution

1
Establish Chain of Custody & Document Assets
Drive serial numbers are recorded in the compliance tracking log and sealed in tamper-evident packaging prior to movement.
Chain-of-custody tracking must initiate before media leaves its secure operational enclosure to prevent unauthorized loss or theft.
2
Execute Magnetic Sanitization (Degaussing)
The internal magnetic fields on the HDD platters and factory timing tracks are permanently disrupted.
Purging data via degaussing renders data unrecoverable while the drive remains physically intact, ensuring data is safe before destruction machinery handling.
3
Execute Physical Destruction (Mechanical Shredding)
The hard drives are shredded into physical metal debris and particulate matter.
Physical destruction ensures total physical impossibility of drive reassembly or head alignment.
4
Perform Destruction Verification
The physical waste output is verified against compliance particle size specifications.
Verification confirms that the physical destruction step met security standards before issuing formal disposition compliance paperwork.
5
Finalize Compliance Documentation
A Certificate of Destruction is generated, signed, attached to serial number logs, and marked closed in asset management.
Legal and regulatory compliance requires formal documentation signed post-destruction to finalize hardware decommission lifecycle.

Key Concept

Enterprise Media Sanitization Lifecycle & Chain of Custody Protocol
Question 9Question →

A help desk technician is troubleshooting a Windows 11 enterprise workstation that continuously redirects web requests to malicious advertising sites, frequently exhibits pop-up windows, and reverts proxy settings to a rogue IP address. Place the following remediation steps in the correct order to eliminate the browser hijack and restore secure functionality.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for resolving a persistent web browser security and redirect compromise is: 1) Disconnect the workstation from the network, 2) Inspect the local hosts file, remove rogue extensions, and reset proxy settings, 3) Execute a thorough anti-malware scan and reset browser configurations to defaults, 4) Reconnect to the network, apply browser updates, and verify functionality, 5) Provide end-user security awareness training.
The correct sequence adheres to CompTIA troubleshooting and malware remediation methodologies: network isolation first, removal of persistence mechanisms (hosts file, proxy settings, extensions) second, anti-malware scanning and browser defaults reset third, system/browser updates and verification fourth, and end-user security awareness training fifth.

Step-by-Step Solution

1
Isolate the infected machine from the network.
Stops communication with malicious external servers and prevents ongoing data exfiltration or payload downloads.
Security best practices dictate isolating compromised systems prior to remediation.
2
Remove persistence mechanisms (hosts file edits, rogue extensions, manual proxy overrides).
Disables active malicious redirection mechanisms causing browser pop-ups and traffic re-routing.
If proxy overrides or hosts modifications remain, traffic will continue to redirect even after browser restarts.
3
Run full anti-malware scanning and reset browser settings.
Removes underlying adware/malware payloads and restores default search engine and homepage settings.
A browser reset ensures all hidden malicious scripts and corrupted web data are removed.
4
Reconnect network, patch software, and verify resolution.
Ensures vulnerabilities are remediated and browser pop-up blockers function properly.
Applying patches prevents re-infection from known browser vulnerabilities.
5
Document findings and educate the user.
Helps the user identify social engineering tactics and suspicious pop-up installation prompts.
Prevents future security breaches caused by human error.

Key Concept

Browser Hijack and Pop-Up Remediation Procedure
Question 10Question →

An IT technician detects suspicious network traffic originating from a workstation on the corporate network. Arrange the basic incident response steps in the correct chronological order from first to last according to standard CompTIA procedures.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of incident response steps is: 1. Identify and confirm the security incident, 2. Report the incident to the designated security team or management, 3. Isolate the affected workstation from the network, and 4. Preserve evidence and document the chain of custody.
According to standard CompTIA incident response guidelines, a first responder must first identify that an incident is taking place. Once identified, the technician reports the incident to appropriate supervisors or incident response management. Next, the affected system is isolated from the network to prevent further damage or data exfiltration. Finally, evidence preservation and chain of custody documentation are performed to maintain legal integrity.

Step-by-Step Solution

1
Identify the incident
The initial security anomaly is detected and verified.
Incident response begins by identifying an event as a security incident.
2
Report the incident
Security personnel and management are informed.
Reporting ensures proper authorization and escalation protocols are followed.
3
Isolate the system
The device is disconnected from network communication.
Isolation contains the incident and prevents lateral movement of threats.
4
Preserve evidence and log custody
Digital evidence is secured and logged for forensic analysis.
Preservation must occur in a controlled manner after the system is contained.

Key Concept

Standard First Responder Incident Response Lifecycle
Question 11Question →

A field technician is assigned to clean heavy industrial dust and particulate buildup from the internal components of a server node deployed in a harsh manufacturing facility. To adhere to CompTIA safety standards regarding personal protection, static control, and hardware preservation, in what sequential order should the technician perform the steps for this maintenance procedure?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct procedural sequence is: 1) Disconnect all power sources and transport the unit to a well-ventilated area while wearing PPE; 2) Connect the server chassis to an ESD grounding system; 3) Immobilize the internal cooling fan blades to prevent back-EMF generation; 4) Displace dust using a specialized ESD-safe vacuum or grounded compressed air unit; 5) Wipe down external surfaces with a lint-free cloth and inspect filters before re-installation.
The correct sequence prioritizes technician safety and power isolation first (disconnecting power, using PPE, and working in a ventilated area). Next, static safety is established by bonding the chassis to ground. Third, internal mechanical components (fans) are secured to prevent electrical generation from back-EMF. Fourth, specialized ESD-safe tools clear internal debris. Finally, surface finishing and filter inspection take place before restoring power.

Step-by-Step Solution

1
Ensure physical safety, power isolation, and proper ventilation with PPE.
The server is de-energized, isolated from live power, and moved to an area where airborne dust won't contaminate office or server room air or harm the technician.
Personal safety (respirator/goggles) and environmental containment are the primary concerns prior to disturbing heavy particulate.
2
Establish ESD grounding controls.
The equipment chassis and technician are at the same ground potential, preventing static discharge damage to sensitive silicon chips.
Air movement across dry surfaces generates substantial triboelectric static charges, making grounding essential before using air tools.
3
Secure fan impellers against free rotation.
Cooling fan motors cannot act as electrical generators when high-velocity air hits them.
Forced air spinning unsecured fan blades turns the DC fan motor into a generator, sending destructive back-EMF voltage into delicate motherboard circuits.
4
Remove internal dust using specialized ESD-safe equipment.
Particulate matter is removed without static accumulation or component damage.
Standard household vacuums accumulate massive static charges on plastic nozzles; specialized ESD vacuums or grounded air tools are mandatory.
5
Perform final cleanup, surface wipe down, and pre-deployment inspection.
Residual dust is cleaned, intake filters are verified, and the system is safely prepared to return to operational service.
Final physical verification ensures no loose debris or blocked air paths remain before re-applying power.

Key Concept

Environmental Controls and ESD Safety Procedures for System Maintenance
Question 12Question →

A systems administrator is planning to upgrade the primary directory service schema for a corporate network. To ensure compliance with standard IT operational procedures, place the following change management phases in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: first, define the purpose and scope of the proposed modification; second, perform a risk assessment and construct a detailed backout plan; third, submit the change proposal to the Change Advisory Board (CAB) for formal approval; and finally, notify impacted users and implement the modification during an approved maintenance window.
The standard CompTIA change management workflow follows a specific logical lifecycle: identifying the purpose and scope of the change comes first, followed by analyzing business risks and drafting a comprehensive backout plan. Once the change package is prepared, it is submitted to the Change Advisory Board (CAB) for formal review and authorization. Finally, after approval is granted, affected stakeholders are notified and the change is deployed within a scheduled maintenance window.

Step-by-Step Solution

1
Identify the initial planning phase
Define the purpose and scope of the proposed change
Before any operational changes are submitted or analyzed, the administrator must clearly document what is being changed and the rationale behind it.
2
Identify risk assessment and mitigation planning
Perform a risk assessment and construct a detailed backout plan
Understanding potential impacts and creating a rollback procedure are mandatory prerequisite elements of a formal change request.
3
Identify the approval authority milestone
Submit the change proposal to the Change Advisory Board (CAB) for formal approval
The CAB reviews the completed change request, risk assessment, and backout plan before granting authorization to proceed.
4
Identify the execution and communication phase
Notify impacted users and implement the modification during an approved maintenance window
Execution and user notification take place only after authorization has been granted by the governing body.

Key Concept

Standard Change Management Process Lifecycle
Question 13Question →

A senior infrastructure administrator is planning a major upgrade to an enterprise directory service schema across an organization's domain controllers. Place the standard change management phases in the correct chronological order from first step to final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper change management sequence begins by defining the purpose and scope, followed by performing a risk assessment and documenting a backout plan, then obtaining Change Advisory Board (CAB) approval, and finally notifying end users while scheduling the maintenance window.
In standard ITIL and CompTIA change management workflows, the initial step is defining the purpose and scope of the proposed change. Next, engineers evaluate potential risks and construct a comprehensive backout plan. Once these prerequisites are met, the request is submitted to the Change Advisory Board (CAB) for formal review. Upon receiving CAB approval, administrators notify affected end users and schedule the implementation within an authorized maintenance window.

Step-by-Step Solution

1
Define purpose and scope
The exact baseline requirements and boundaries of the change are documented.
Every change request must start with a clear objective and defined scope before further planning can occur.
2
Perform risk assessment and prepare backout plan
Impact analysis is completed and a detailed rollback procedure is established.
Understanding potential failure modes and having a backout plan is mandatory for approval consideration.
3
Submit for Change Advisory Board (CAB) authorization
Formal review and approval from key stakeholders are obtained.
CAB oversight ensures that business risk and schedule conflicts are fully addressed prior to implementation.
4
Notify end users and schedule maintenance window
Stakeholders are informed and execution timing is established.
User notification and downtime scheduling must only take place after formal change approval has been granted.

Key Concept

Change Management Process Lifecycle
Question 14Question →

A technician is preparing to replace a swollen internal Lithium-ion battery in a corporate laptop. Place the following repair steps in the correct order from first to last to safely complete the battery replacement process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for safely replacing an internal swollen battery is: 1) Disconnect external AC power and shut down the laptop; 2) Remove the bottom enclosure panel; 3) Disconnect the internal battery power harness from the motherboard; 4) Unfasten and place the swollen battery in a fire-safe container; 5) Install the replacement battery, connect its harness, and secure the chassis cover.
The proper ordering prioritizes safety and electrical protection: disconnect external power first, open the enclosure, isolate internal electrical energy by disconnecting the battery connector from the motherboard, safely extract and contain the hazardous swollen battery, and finally install the replacement and close the chassis.

Step-by-Step Solution

1
Isolate external power sources.
The AC adapter is unplugged and the laptop is completely powered off.
Prevents electrical shock and guards against accidental power delivery during initial handling.
2
Open the laptop lower casing.
The bottom chassis cover is removed, exposing internal components.
Access to non-removable internal laptop batteries requires removing the base plate.
3
Isolate internal electrical circuits.
The battery harness is detached from the system motherboard connector.
Disconnecting internal battery power before loosening internal screws prevents tool-induced short circuits on the motherboard.
4
Remove and contain the compromised battery.
The swollen Li-ion battery is unfastened and placed into a hazardous thermal safety vessel.
Physical swelling indicates gas accumulation inside cells; immediate isolation in a fire-safe storage container prevents fire hazards.
5
Install replacement hardware and close enclosure.
New battery is seated, wired to the system board, and base chassis is closed.
Restores laptop operation to a safe, functional state.

Key Concept

Internal Swollen Battery Safe Replacement Procedure
Estimated Time:1m 30s
Question 15Question →

A technician needs to manually add an enterprise network multifunction printer (MFD) to a client workstation using the device's static IP address and vendor-supplied driver files. In what sequence should the technician perform the steps to complete this configuration?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with obtaining the static IP address from the MFD, opening the workstation printer setup wizard to add a printer by IP, creating the Standard TCP/IP Port, installing the manufacturer driver via 'Have Disk', and finally configuring default printing preferences.
The correct order follows standard operating system procedure: first obtaining the device's static IP address, selecting manual IP printer setup, creating the standard TCP/IP port, specifying the vendor driver via 'Have Disk', and setting printing defaults.

Step-by-Step Solution

1
Retrieve the printer's static network IP address.
Identified target IP address.
Network printing requires the exact destination IP address to configure a network port.
2
Launch the Add Printer Wizard on the workstation.
Initiated manual TCP/IP printer installation.
Manual installation bypasses automatic network discovery when using specific IP parameters.
3
Input the static IP address to establish the port.
Created a Standard TCP/IP Port.
The OS requires a designated communication endpoint to send print spools over the network.
4
Locate vendor-supplied driver files using 'Have Disk'.
Installed the custom printer driver.
Vendor drivers ensure full compatibility and access to hardware features over generic drivers.
5
Adjust printing defaults in Printing Preferences.
Finalized client default settings like double-sided printing.
Default options take effect for all subsequent print jobs sent from this workstation.

Key Concept

Manual Network Printer Installation via Standard TCP/IP Port
Question 16Question →

A technician receives an alert that one hard drive in a hot-swappable RAID 1 array has failed, causing the array to run in a degraded state. What is the correct sequence of steps the technician should take to restore full redundancy to the RAID array?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: 1) Identify the failed physical drive using enclosure LEDs or RAID management software, 2) Release the carrier latch and remove the failed drive from the hot-swap drive bay, 3) Insert a new replacement drive of equal or greater capacity into the hot-swap bay, and 4) Verify that the RAID controller initiates the array rebuild process to restore fault tolerance.
The standard procedure for replacing a failed hot-swappable drive in a degraded RAID array begins with identifying the specific failed drive using status LEDs or management utility software. Next, the technician disengages and removes the faulty drive from its slot. A new replacement disk of sufficient capacity is then inserted into the empty slot. Finally, the technician verifies or initiates the RAID rebuild process using the controller interface to synchronize data and re-establish fault tolerance.

Step-by-Step Solution

1
Locate the failed drive
Identified the exact bay housing the faulty drive.
Prevents accidental extraction of an operational disk, which would crash a degraded RAID 1 volume.
2
Remove the faulty drive while system remains online
The failed drive is extracted from the server.
Hot-swappable drive enclosures permit removal without powering down the entire system.
3
Install the replacement drive
The new drive is seated securely in the bay.
The RAID volume requires a replacement drive meeting capacity specifications to host mirrored data.
4
Initiate/Confirm rebuild
The array rebuilds data onto the new drive.
Full fault tolerance and redundancy are restored once data synchronization completes.

Key Concept

Hot-Swappable RAID 1 Drive Replacement and Array Rebuilding Procedure
Question 17Question →

A network technician receives an escalation ticket regarding a high-volume workgroup laser printer. Users report that printed pages contain smeared, unfused toner that wipes off easily when touched. Arrange the technician's troubleshooting and remediation steps in the correct chronological order according to the standard CompTIA troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the six steps of the CompTIA troubleshooting methodology: (1) Review user feedback and inspect output pages; (2) Formulate a hypothesis regarding fuser heating failure; (3) Execute hardware diagnostic tests to confirm the heating failure; (4) Power down, cool, and replace the fuser module; (5) Power on and print test pages to verify full functionality; (6) Record all findings, root cause, and replacement details in the service desk ticketing system.
The correct order strictly adheres to CompTIA's 6-step troubleshooting methodology: 1. Identify the problem (inspecting pages and reviewing user reports), 2. Establish a theory of probable cause (attributing unfused toner to a fuser issue), 3. Test the theory (running diagnostic tests to confirm temperature failure), 4. Plan and implement the solution (powering off, cooling, and replacing the fuser), 5. Verify full system functionality (printing test pages), and 6. Document findings, actions, and outcomes (logging ticket details).

Step-by-Step Solution

1
Identify the problem
Gather symptoms and inspect printed output showing unfused toner.
Always begin by gathering details from the user and inspecting physical evidence to define the issue scope.
2
Establish a theory of probable cause
Deduce that the fuser assembly is not reaching melting temperature.
Unfused toner wiping off paper indicates the fuser heat/pressure mechanism is malfunctioning.
3
Test the theory to determine the cause
Run diagnostic tests to confirm the fuser unit failure.
Verification of the hypothesis is required before purchasing or performing physical part replacements.
4
Establish a plan of action and implement the solution
Safely replace the defective fuser assembly.
Implementation occurs after safety precautions (powering off and cooling down hot components) are met.
5
Verify full system functionality
Print test pages and verify proper toner bonding.
Testing ensures the issue is completely resolved before turning the system back over to users.
6
Document findings, actions, and outcomes
Log full details into the ticketing system.
Final documentation creates a historical reference for future technicians and closes out the ticket.

Key Concept

CompTIA Troubleshooting Methodology Applied to Laser Printer Fuser Issues
Question 18Question →

An IT specialist needs to configure a newly installed multifunction device (MFD) to enable secure Scan-to-Email functionality using authenticated SMTP over TLS across different network subnets. Which sequence represents the correct order of administrative steps to properly establish and verify this configuration from start to finish?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order begins with setting network IP parameters and DNS on the EWS, followed by entering the SMTP server address and port, enabling TLS with authentication credentials, defining the sender email address, and lastly running a test scan from the control panel.
Configuring Scan-to-Email on an enterprise MFD requires establishing basic network connectivity (IP/DNS) first. Once the network layer is functional, higher-level application settings (SMTP server address/port), security credentials (TLS/login), and sender attributes (From address) are defined sequentially before conducting an end-to-end operational test.

Step-by-Step Solution

1
Assign network identity and address parameters
The MFD achieves layer 3 IP connectivity and name resolution capabilities via primary DNS.
Without valid IP addressing and DNS, the MFD cannot resolve the mail server FQDN or route packets beyond its local subnet.
2
Configure outgoing SMTP server location settings
The device knows where to route outbound email traffic.
The destination server address and port must be specified before security handshake rules can be applied.
3
Enable cryptographic transport security and supply authentication credentials
Encrypted communication channels and login mechanisms are set up for outgoing SMTP connections.
Modern mail gateways reject unauthenticated or unencrypted mail relay requests.
4
Set system default sender header identity
Outbound messages are populated with valid envelope header sender details.
Anti-spam and mail gateway policies require a valid sender address in the 'From' field.
5
Execute end-to-end verification via control panel scan test
The email arrives in the target mailbox, confirming full functionality.
Testing validates the entire chain from physical capture to network routing and server authentication.

Key Concept

MFD Network Scan-to-Email Configuration Workflow
Question 19Question →

An IT technician is training a junior technician on laser printer operations. Place the following primary stages of the electrophotographic (EP) printing process in the correct order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of the EP printing process stages is Charging, Exposing, Developing, Transferring, and Fusing.
The standard operational sequence for electrophotographic (EP) laser printing begins with Charging (conditioning the drum surface with high negative voltage), followed by Exposing (laser writes the latent image by neutralizing exposed areas), Developing (toner adheres to the exposed drum areas), Transferring (paper is charged to attract toner off the drum), and Fusing (heat and pressure permanently bind toner to paper).

Step-by-Step Solution

1
Identify the initial conditioning phase.
Charging (item_1) is the first step.
The photosensitive drum must be uniformly charged before any image can be written onto it.
2
Identify the image creation phase.
Exposing (item_2) is the second step.
The laser writes the latent image by altering charges on the drum surface.
3
Identify the toner application phase.
Developing (item_3) is the third step.
Toner is transferred onto the drum where the laser exposed it.
4
Identify the paper transfer phase.
Transferring (item_4) is the fourth step.
An opposing charge pulls the toner from the drum onto the physical paper.
5
Identify the final bonding phase.
Fusing (item_5) is the fifth step.
Heat and pressure permanently melt the toner into the paper.

Key Concept

Electrophotographic (EP) Printing Process Steps
Question 20Question →

A systems administrator wants to capture CPU utilization data over an extended period into a log file using Performance Monitor. Place the administrative steps required to create a custom User Defined Data Collector Set in the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with launching Performance Monitor using perfmon.msc, opening the Data Collector Set wizard under User Defined, configuring manual selection for performance counters, and finally choosing the Processor counters before completing the setup.
To create a custom performance log in Windows, an administrator must first open Performance Monitor via perfmon.msc, initiate a new Data Collector Set from the User Defined context menu, configure the wizard for manual counter collection, and lastly select the appropriate CPU counters before saving the collector set.

Step-by-Step Solution

1
Launch Performance Monitor by executing perfmon.msc.
The Performance Monitor MMC utility opens.
You must open the tool before managing data collectors.
2
Navigate to Data Collector Sets > User Defined and select New > Data Collector Set.
The Create New Data Collector Set wizard opens.
User Defined collector sets allow custom counter logging.
3
Name the set and select 'Create manually (Advanced)' followed by 'Performance counter'.
The wizard advances to the counter selection screen.
Manual setup allows customization of specific objects and counters.
4
Click Add to select the Processor counters, set the sample interval, and complete the wizard.
The custom Data Collector Set is saved and ready to run.
Adding the CPU metrics defines what data will be collected in the log file.

Key Concept

Creating Performance Monitor Data Collector Sets
Page 1 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin