CompTIA A+ / Network+ / Security+ CompTIA A+ Core 1: Hardware, Mobile Devices & Networking (220-1101) Flashcards

24 sample cards from the CompTIA A+ Core 1: Hardware, Mobile Devices & Networking (220-1101) deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. List the seven steps of the laser printing (imaging) process in order.

   1. Processing, 2. Charging, 3. Exposing, 4. Developing, 5. Transferring, 6. Fusing, 7. Cleaning. (Mnemonic: 'Please Come Every Day To Find Cookies.') The drum is charged, the laser exposes/writes the image, toner is developed onto it, transferred to paper, fused with heat, and the drum is cleaned.

2. Define the three NIST cloud service models: IaaS, PaaS, and SaaS.

   IaaS (Infrastructure as a Service) provides virtual hardware—VMs, storage, networking—that the customer manages. PaaS (Platform as a Service) provides a development/runtime platform so customers deploy apps without managing the OS/hardware. SaaS (Software as a Service) delivers ready-to-use applications over the internet (e.g., webmail).

3. Compare public, private, hybrid, and community cloud deployment models.

   Public cloud is shared infrastructure owned by a provider, available to anyone (multi-tenant). Private cloud is dedicated to a single organisation. Hybrid combines public and private with orchestration between them. Community cloud is shared by several organisations with common requirements.

4. Define the key cloud characteristics: rapid elasticity, on-demand self-service, resource pooling, and measured service.

   Rapid elasticity: resources scale up/down quickly with demand. On-demand self-service: users provision resources automatically without provider intervention. Resource pooling: a multi-tenant model sharing pooled resources. Measured service: usage is metered so you pay only for what you consume.

5. Distinguish a Type 1 from a Type 2 hypervisor in client-side virtualisation.

   A Type 1 (bare-metal) hypervisor runs directly on the hardware with no host OS (e.g., ESXi, Hyper-V), offering better performance for servers. A Type 2 (hosted) hypervisor runs as an application on top of a host OS (e.g., VirtualBox, VMware Workstation), common for desktop/client-side virtualisation.

6. What are the resource requirements and one purpose of a sandbox in client-side virtualisation?

   Each VM needs adequate CPU (with VT-x/AMD-V enabled), RAM, disk space, and network resources allocated from the host. A sandbox is an isolated VM/environment used to safely test software or analyse malware without affecting the host system.

7. List the six steps of the CompTIA troubleshooting methodology in order.

   1. Identify the problem. 2. Establish a theory of probable cause (question the obvious). 3. Test the theory to determine cause. 4. Establish a plan of action and implement the solution. 5. Verify full system functionality and implement preventive measures. 6. Document findings, actions, and outcomes.

8. In the troubleshooting methodology, what should you always consider during the 'identify the problem' step regarding changes and backups?

   Gather information, question the user, identify symptoms, determine if anything recently changed, and—critically—perform backups before making changes. Also inquire about environmental or infrastructure changes so you don't lose data or overlook a recent modification as the cause.

9. What do common POST beep codes and POST/diagnostic indicators help you diagnose, and what does a single beep usually mean?

   POST (Power-On Self-Test) beep codes and on-board LEDs/codes report hardware faults found at boot (RAM, GPU, CPU). The pattern is vendor-specific, but a single short beep typically indicates a successful POST/normal boot. Repeated or patterned beeps usually indicate a memory or video failure.

10. What are the symptoms and likely causes of failing RAM?

    Symptoms: random reboots, frequent BSODs/lock-ups, failure to boot with POST beeps, or memory errors. Causes: faulty or improperly seated modules, incompatible/mismatched RAM. Diagnose by reseating, testing one module at a time, or running a memory diagnostic (e.g., Windows Memory Diagnostic / MemTest).

11. What symptoms point to a failing or inadequate power supply, and how do you confirm it?

    Symptoms: no power at all, intermittent shutdowns/reboots, system powers on then dies, burning smell, or instability under load. Confirm with a PSU tester or multimeter checking the rail voltages ($+3.3$, $+5$, $+12\ \text{V}$), and verify the fan spins. Replace if voltages are out of tolerance.

12. What does a continuously running/over-spinning fan, or unexpected shutdowns, indicate about a CPU/motherboard, and what causes thermal shutdown?

    It indicates overheating. Unexpected shutdowns are often the system's thermal protection cutting power to prevent CPU damage. Causes include failed/clogged fans, dried-out thermal paste, dust buildup, or a failing heat sink. Reapply thermal paste, clean dust, and ensure fans/airflow work.

13. What are common indicators of an impending hard-drive (storage) failure?

    Indicators: read/write errors, slow performance, frequent crashes, clicking or grinding noises (HDD), S.M.A.R.T. warnings, files becoming corrupt or disappearing, and extended/loud boot times. Back up data immediately and run diagnostics; replace the drive.

14. What does a RAID controller report when an array is degraded, and what is the correct action for a single failed disk in RAID 5?

    A degraded array means one disk has failed but data is still accessible via parity/mirroring. For RAID 5 with one failed disk, replace the failed drive promptly and let the array rebuild from parity. Do not delay—a second disk failure before rebuild completes causes total data loss.

15. What does the message 'RAID not found' or array failing to initialise typically indicate at boot?

    It usually indicates a controller, cabling, or multiple-drive failure, an incorrectly configured/missing RAID configuration, or the drives not being detected. Check power and data cables, the controller/BIOS RAID settings, and whether more disks than the array's tolerance have failed.

16. What are the likely causes of a dim laptop display, flickering, or no image, and how do you isolate them?

    Dim screen: failed backlight/inverter or low brightness setting. Flickering: loose display cable, failing inverter, or driver issue. No image: connect an external monitor—if external works, the LCD panel/cable/backlight is faulty; if not, the GPU or board is at fault.

17. List common mobile device display/touch faults and their typical fixes.

    Dim or no display: check brightness, auto-brightness sensor, or replace backlight/screen. Unresponsive/erratic touch: recalibrate, remove screen protector, replace digitiser, or restart. Flickering/artifacts: faulty display or loose connector. Overheating can also cause dimming and shutdowns.

18. Outline the structured approach to troubleshooting no network connectivity on a workstation.

    Check physical link/LED lights and cable first. Verify IP configuration with ipconfig/ifconfig (an APIPA $169.254.x.x$ address means DHCP failed). Test loopback ($127.0.0.1$), then the default gateway, then an external IP, then a DNS name to isolate whether the issue is local, gateway, or DNS.

19. What does an APIPA address ($169.254.x.x$) on a client indicate?

    It indicates the client failed to obtain an address from a DHCP server and self-assigned an Automatic Private IP Address. Causes include an unreachable/offline DHCP server, a bad cable/switch port, or exhausted DHCP scope. The device can only communicate on the local link, not beyond it.

20. Which command-line tools test latency and trace the path to a remote host, and what does each show?

    ping tests reachability and round-trip latency to a host using ICMP. tracert (Windows) / traceroute (Linux) shows each router hop along the path and the latency at each, helping locate where connectivity slows or fails. pathping combines both.

21. What are the causes and fixes for poor or intermittent wireless connectivity?

    Causes: weak signal/distance, interference (other APs, microwaves, $2.4\ \text{GHz}$ congestion), channel overlap, or wrong band. Fixes: move closer or add an AP/repeater, change to a less congested channel (1/6/11) or the $5\ \text{GHz}$ band, update drivers, and check antenna connections.

22. What are the symptoms and causes of laser printer faults: a repeating spot/mark, smudged toner, and ghost/faded images?

    Repeating spots at regular intervals = a defect on the drum or roller. Toner that smudges or rubs off = a failed fuser (not bonding toner). Faded/ghost images = low toner, a worn drum, or fuser/charge issues. Vertical streaks indicate a scratched drum or debris on the corona wire.

23. What causes paper jams in printers and what are key preventive steps?

    Causes: worn/dirty pickup rollers, wrong or damp paper, overfilled tray, debris, or a faulty fuser/feed assembly. Prevention: use the correct paper weight, store paper dry, don't overfill, clean rollers, and ensure the paper path is clear and components (separation pad, rollers) are in good condition.

24. For an inkjet printer producing lines or gaps in output, what maintenance steps should you perform?

    Run the printer's nozzle/head cleaning cycle to clear clogged nozzles, then run a print-head alignment and nozzle-check pattern. Replace empty or dried cartridges. If cleaning fails repeatedly, the print head may need replacement. Use the printer regularly to prevent ink drying.

What this deck covers

CompTIA A+ Core 1: Hardware, Mobile Devices & Networking (220-1101) flashcards FAQ