Pustakam Library

Free Exams learning guide

CompTIA A+ Exam Prep: Complete Study Guide

CompTIA A+ Exam Prep: Complete Study Guide — a free intermediate-level guide covering how to pass the comptia a+ exam. Learn with clear explanations,...

94 min read10 chaptersintermediate

What you will learn

  1. Exam Strategy & Study Planning
  2. PC Hardware Components & Peripherals
  3. Mobile Devices & Wearable Technology
  4. Networking Fundamentals
  5. Virtualization & Cloud Computing
  6. Hardware & Network Troubleshooting
  7. Operating Systems Installation & Management
  8. Security Fundamentals
  9. Software Troubleshooting
  10. Operational Procedures & Professionalism

1. Exam Strategy & Study Planning

The Two-Exam Hurdle: Core 1 and Core 2 Demystified Imagine sitting for the CompTIA A+ exam. You’ve studied for months, memorized port numbers, mastered subnetting, and can troubleshoot a blue screen of death in your sleep. The exam begins, and your first question isn't a multiple-choice question about Wi-Fi frequencies. Instead, you are staring at a simulated motherboard, asked to drag and drop the correct RAM modules into the right slots to meet a specific upgrade requirement. This is the reality of the modern CompTIA A+ certification. It is no longer a simple test of rote memorization. The exam has evolved to validate practical, hands-on problem-solving skills. For an intermediate learner, your goal isn't just to learn the material; it's to master the exam's structure, anticipate its traps, and engineer a study plan that bridges the gap between theoretical knowledge and practical execution. The CompTIA A+ certification (Exam codes 220-1101 and 220-1102) consists of two distinct exams. You must pass both to become certified. While they cover overlapping themes, their focuses are distinctly different. Core 1 (220-1101) leans heavily into hardware, networking, mobile devices, and cloud computing. It is the "infrastructure" exam. You will be expected to understand how things connect, communicate, and are physically assembled. Core 2 (220-1102) shifts the focus to operating systems, security, software troubleshooting, and operational procedures. It is the "software and operations" exam, testing how you manage, secure, and support the infrastructure. Domain Weightings: Where to Spend Your Energy CompTIA publishes exact domain weightings for each exam. These percentages are not just administrative trivia; they are your strategic blueprint. If a domain accounts for 25% of the exam, roughly 25% of your study time should be dedicated to it. Core 1 (220-1101) Weightings: Mobile Devices (15%): Laptops, tablets, smartphones, and wearables. Networking Technology (20%): Ports, protocols, routers, switches, and cabling. Hardware (25%): PC components, peripherals, and printers. Virtualization & Cloud Computing (11%): Hypervisors, IaaS, PaaS, SaaS, and cloud concepts. Hardware & Network Troubleshooting (29%): Methodology and resolving issues across the previous domains. Core 2 (220-1102) Weightings: Operating Systems (31%): Windows, macOS, Linux, and mobile OS management. Security (25%): Threats, vulnerabilities, encryption, and access controls. Software Troubleshooting (22%): Resolving OS and application issues. Operational Procedures (22%): Documentation, change management, safety, and professionalism. Notice that in Core 1, Hardware and Troubleshooting combine for over half the exam. In Core 2, Operating Systems and Security dominate. As an intermediate learner, you likely already have a baseline understanding of hardware and OS navigation. Your study plan must identify exactly where in these domains your knowledge gaps lie. Anatomy of the Exam: Format, Question Types, and Scoring Understanding how CompTIA asks questions is just as important as knowing the answers. …

2. PC Hardware Components & Peripherals

A technician receives a ticket: "User's PC won't turn on. Makes a weird beeping noise." When they arrive, they press the power button, hear three short beeps, and the screen stays black. Rather than immediately dismantling the PC or assuming the motherboard is dead, the technician checks the beep code against the motherboard manual. Three short beeps indicate a memory error. They pop open the case, reseat the RAM modules, and the machine boots flawlessly. This scenario perfectly illustrates why the CompTIA A+ exam heavily emphasizes hardware. As established in Chapter 1, Hardware accounts for 25% of the Core 1 (220-1101) exam. But more importantly, hardware knowledge is the foundation for the Hardware & Network Troubleshooting (29%) domain. You cannot troubleshoot what you do not fundamentally understand. The Core Internal Components Every PC is a symphony of interconnected parts. Understanding how these components communicate and draw power is critical for both the exam and real-world repairs. Motherboards, CPUs, and RAM The Motherboard is the central nervous system of the PC. It houses the CPU (Central Processing Unit), RAM (Random Access Memory), and expansion slots, acting as the communication hub for all peripherals. When selecting or replacing a motherboard, you must ensure socket compatibility with the CPU. Intel and AMD use specific socket types (e.g., Intel's LGA 1700 or AMD's AM4/AM5). The socket type dictates the physical shape of the CPU and the pin layout. The CPU acts as the brain of the computer. Modern CPUs generate immense heat, requiring a heatsink and fan (often combined into a "cooler"). Between the CPU and the heatsink, a technician must apply thermal paste to fill microscopic air gaps and ensure efficient heat transfer. Failing to apply thermal paste correctly will cause the CPU to rapidly overheat and throttle or shut down. RAM is the system's short-term memory. It is volatile, meaning it loses its data when power is removed. For the exam, you need to differentiate between modern RAM form factors: DIMM (Dual In-line Memory Module): Used in desktop computers. SO-DIMM (Small Outline DIMM): Used in laptops and small form-factor PCs. RAM speeds are measured in MHz or MT/s (MegaTransfers per second). When upgrading, you must match the RAM generation (e.g., DDR4 vs. DDR5) to what the motherboard supports. Mixing RAM speeds is possible, but the system will default to the speed of the slowest installed module. Storage Devices Storage provides the non-volatile memory where the operating system, applications, and user data permanently reside. The days of IDE ribbons are long gone; modern storage revolves around SATA and NVMe interfaces. HDD (Hard Disk Drive): Traditional mechanical storage. While slower, they offer high capacities at low costs. They connect via SATA. SATA SSD (Solid …

3. Mobile Devices & Wearable Technology

A marketing executive drops off her company-issued laptop and her personal smartphone with a panicked look. The laptop won't hold a charge, and her phone refuses to sync calendar updates to the cloud. She has a client presentation in two hours. As an IT support technician, you don't have time to marvel at the miniaturization of modern technology—you need to know exactly how to crack open that laptop safely, swap the battery, and reconfigure her mobile synchronization settings on the fly. The Mobile Devices (15%) domain of the Core 1 (220-1101) exam tests exactly this kind of practical agility. While the foundational concepts of hardware were established in PC Hardware Components & Peripherals, mobile devices require a different approach to maintenance, configuration, and troubleshooting. Laptop Hardware: Disassembly and Reassembly Unlike standard desktop towers with their standardized ATX form factors and plug-and-play PCIe slots, laptops are masterclasses in spatial efficiency. Every millimeter matters, which means components are stacked, ribboned, and screwed together in highly specific sequences. The Golden Rules of Laptop Teardown Before disassembling any laptop, remember that the Hardware Simulations on the 220-1101 exam will actively test your adherence to proper procedures. 1. Document Everything: Take photos or draw diagrams at every step. Note screw sizes and locations, as a screw that is too long can puncture a battery or motherboard. 2. Use the Right Tools: A standard Phillips-head isn't always enough. You will frequently need plastic spudgers or pry tools to unclip plastic bezels without marring them. 3. Battery First, Always: Disconnect the battery before touching any other internal component. Even when powered off, a laptop motherboard receives standby power. 4. Antistatic Precautions: Use an ESD wrist strap and mat. Laptops are far less forgiving of static discharge than desktops due to tightly integrated components. Swapping Core Components The exam expects you to know the physical procedure for replacing RAM, storage (SSD), and the keyboard. RAM: Modern laptops typically use SO-DIMM (Small Outline Dual In-line Memory Module) sticks. Replacement involves locating the RAM bay (sometimes hidden under the keyboard deck), pushing outward on the two metal retaining clips, and allowing the stick to pop up at a 30-degree angle for removal. Some modern ultrabooks use soldered LPDDR memory, which cannot be upgraded—a fact you must recognize on the exam. SSD: Laptops primarily use M.2 NVMe drives. To remove one, you unscrew the single retention screw at the back of the drive. The drive will spring up slightly, allowing you to pull it out. Older laptops may use 2.5-inch SATA drives, which slide out of caddies. Battery: External batteries feature release latches. Internal batteries require you to remove the bottom casing and disconnect the battery cable from the motherboard. Warning: …

4. Networking Fundamentals

The TCP/IP Model and Core Protocols Imagine a user clicks a link to load a company portal. In the seconds that follow, their workstation negotiates a hardware address with the router, translates a domain name to an IP address, establishes a connection with a remote server, and requests a specific file—all while ensuring the data arrives intact. This entire process is governed by the TCP/IP model, the conceptual framework that dictates how data travels across modern networks. As an intermediate IT professional, you already know that networks exist to move data. For the CompTIA A+ Core 1 (220-1101) exam, you need to understand exactly how that data is packaged, addressed, and transported, as Networking Technology accounts for 20% of your exam score. The TCP/IP model condenses network communication into four layers. While you don't need to memorize the OSI model's seven layers in depth for the A+ exam, understanding the four layers of TCP/IP is mandatory: 1. Link (Network Access) Layer: Handles physical addressing (MAC addresses) and how data is put onto the physical medium (cables, wireless). 2. Internet Layer: Handles logical addressing (IP addresses) and routing. This is where IP (Internet Protocol), ICMP (used by ping), and ARP (Address Resolution Protocol) operate. 3. Transport Layer: Manages end-to-end communication. TCP (Transmission Control Protocol) guarantees delivery through handshakes and acknowledgments. UDP (User Datagram Protocol) fires data quickly without guaranteeing delivery, making it ideal for streaming and VoIP. 4. Application Layer: Where user-facing protocols operate. This layer formats data and handles application-specific tasks. Common Protocols and Port Numbers The CompTIA A+ exam heavily tests your knowledge of common protocols and their associated ports. Ports act as logical endpoints, telling the receiving operating system which application should handle the incoming data. You must memorize the following: HTTP (Hypertext Transfer Protocol): Used for unencrypted web traffic. Port: 80 Transport Protocol: TCP HTTPS (Hypertext Transfer Protocol Secure): Used for encrypted web traffic (via TLS/SSL). Port: 443 Transport Protocol: TCP DNS (Domain Name System): Translates human-readable domain names (like example.com) into IP addresses. Port: 53 Transport Protocol: TCP and UDP (UDP for standard queries, TCP for larger zone transfers). DHCP (Dynamic Host Configuration Protocol): Automatically assigns IP addresses, subnet masks, and default gateways to clients. Ports: 67 (Server) and 68 (Client) Transport Protocol: UDP SMTP (Simple Mail Transfer Protocol): Used for sending email from a client to a server or between servers. Port: 25 (unencrypted) or 587 (encrypted/submission) Transport Protocol: TCP IMAP (Internet Message Access Protocol): Used for retrieving email. IMAP syncs emails directly with the server, meaning changes made on the client reflect on the server. Port: 143 (unencrypted) or 993 (secure/IMAPS) Transport Protocol: TCP POP3 (Post Office Protocol version 3): Used for retrieving email. …

5. Virtualization & Cloud Computing

The Virtualization Landscape A small marketing firm needs to test a new application on Windows 11, but their employees use macOS. Rebuying hardware for a single test is prohibitively expensive. Meanwhile, a growing e-commerce site needs to double its server capacity for Black Friday, then shrink back down in January—without purchasing physical machines that will sit idle for eleven months. Both scenarios are solved by the same paradigm shift: separating the computing environment from the physical hardware. For the CompTIA A+ exam, understanding how to configure these environments and how they are delivered over the network you studied in Networking Fundamentals is critical. Virtualization and cloud computing account for 11% of your Core 1 (220-1101) exam, meaning you can expect roughly ten questions on these topics. Client-Side Virtualization Virtualization is the process of using software to create a virtual representation of a physical machine, rather than a physical one. This allows a single physical computer to run multiple independent operating systems simultaneously. The Purpose and Benefits of Client-Side Virtualization Client-side virtualization refers to running virtual machines (VMs) directly on a user’s local workstation. IT professionals use local VMs for several reasons: Legacy Application Support: Running an older OS (like Windows 7) in a VM to support a critical piece of software that is incompatible with the host OS. Cross-Platform Development and Testing: A developer writing code on a Linux host can spin up Windows and macOS VMs to test application compatibility. Sandboxing: Isolating untrusted software or analyzing malware in a controlled environment. If the VM is compromised, the host OS remains safe. Training and Education: Allowing students or new hires to practice administrative tasks without risking the primary workstation. Resource Requirements A virtual machine does not magically generate new hardware; it borrows resources from the physical host. To run client-side virtualization effectively, the host machine must have robust physical components, which build upon the hardware knowledge from PC Hardware Components & Peripherals: CPU: The processor must support hardware-assisted virtualization (Intel VT-x or AMD-V). This feature must be enabled in the host system's BIOS/UEFI. The CPU also needs multiple cores to distribute processing power between the host and guest operating systems. RAM: Memory is the most common bottleneck. If the host has 16GB of RAM, allocating 8GB to a VM leaves the host with only 8GB. A host running multiple VMs requires a massive amount of physical RAM. Storage: VMs are stored as large files (often VHD or VMDK files). They require high-speed storage—preferably NVMe or SATA SSDs—to prevent severe I/O bottlenecks when the host and guest OS read and write to the disk simultaneously. Networking: The host requires a Network Interface Card (NIC) capable of handling the traffic of both …

6. Hardware & Network Troubleshooting

The CompTIA Troubleshooting Methodology A user submits a help desk ticket: "My computer keeps restarting and the screen looks weird." As an IT support technician, your job isn't to guess the cause, but to systematically eliminate variables until the root cause is found. The CompTIA A+ exam expects you to apply a rigid, six-step troubleshooting methodology. Memorize these steps in order, as they frequently appear in multiple-response and drag-and-drop questions. 1. Identify the problem: Gather information from the user, identify user changes to the computer, and perform searches based on symptoms. Ask open-ended questions ("What were you doing when it happened?") followed by closed-ended questions ("Did you hear a beep?"). 2. Establish a theory of probable cause: Look for the obvious first. Is the monitor plugged in? Is the network cable disconnected? 3. Test the theory to determine the cause: If your theory is correct, move to step 4. If it is incorrect, establish a new theory and test it again (return to step 2). Always test safely; do not make permanent changes yet. 4. Establish a plan of action to resolve the problem and implement the solution: Determine what needs to be done (e.g., replace a faulty RAM stick, update a driver) and execute the fix. If the fix impacts the user's workflow or requires downtime, communicate this first. 5. Verify full system functionality and, if applicable, implement preventive measures: Do not just verify that the error stopped. Test the system thoroughly. If a printer jammed due to humidity, implement a preventive measure like relocating the printer or using a dehumidifier. 6. Document findings, actions, and outcomes: Documentation closes the loop. It builds a knowledge base for future issues and provides accountability. Always keep the impact of your actions in mind. If a fix risks destroying data (like running a disk repair utility on a failing hard drive), back up the data before proceeding. If you are unsure about a specific fix, escalate the issue to a senior technician rather than making the problem worse. Diagnosing Hardware Failures Building on the hardware concepts from PC Hardware Components & Peripherals, this section focuses on what happens when those components fail. Hardware failures generally fall into three categories: power, thermal, and POST/boot errors. Power Issues When a machine is completely dead (no lights, no fans, no sound), work from the wall inward. Check the outlet: Is it on a switched circuit? Test it with a known-good device like a lamp. Check the cable and switch: Ensure the voltage switch on the back of the power supply (PSU) is set to the correct regional voltage (115V in North America, 230V in Europe). Verify the I/O switch is flipped to "I" (On). Test …

7. Operating Systems Installation & Management

The Windows Installation Lifecycle A user brings you a laptop with a completely failed hard drive. You replaced the physical hardware using the troubleshooting methodologies covered in Chapter 6, but now you face a blank, unformatted drive. Before the user can get back to work, you must install an operating system from scratch. For the CompTIA A+ Core 2 (220-1102) exam, understanding the Windows installation lifecycle—from booting the installation media to configuring post-installation updates—is critical, as the Operating Systems domain makes up 31% of your score. Booting from Media and Partitioning Whether you are installing Windows 10 or Windows 11, the initial process is largely the same. You will typically boot the system from USB installation media created using the Windows Media Creation Tool. During the setup process, you will reach the "Where do you want to install Windows?" screen. This is where you manage disk partitions. If the drive is new, it will be entirely Unallocated Space. If the drive was previously used, you will see existing partitions (like a primary OS partition and a system recovery partition). For a clean install, you should delete existing partitions until you only have unallocated space, then select that space and click Next. Windows will automatically create the necessary partitions: - System Partition (EFI/ESP): Usually 100MB, formatted as FAT32. It holds the boot manager and boot files. - Microsoft Reserved Partition (MSR): Usually 16MB, used for disk management operations. - Windows Partition (C:): The primary partition formatted as NTFS where the OS is installed. Windows 10 vs. Windows 11 Requirements While the installation workflow is similar, the hardware requirements diverge sharply with Windows 11. You must know these differences for the exam. Windows 10 Requirements: - 1 GHz processor (2 cores for 64-bit) - 2 GB RAM (64-bit) - 32 GB storage - DirectX 9 graphics with WDDM 1.0 driver - BIOS/UEFI firmware Windows 11 Requirements: - 1 GHz processor (2 cores minimum) - 4 GB RAM - 64 GB storage - DirectX 12 compatible graphics / WDDM 2.0 - UEFI firmware with Secure Boot capability - TPM 2.0 (Trusted Platform Module) If you try to install Windows 11 on hardware lacking a TPM 2.0 chip or a modern CPU, the installer will halt and display a compatibility error. Activation and Updates Once the OS is installed, it must be activated. Windows uses Digital Licenses (tied to the hardware signature or a Microsoft account) or traditional Product Keys (25-character codes). If the motherboard was replaced, the digital license may fail, requiring you to run the Activation Troubleshooter to re-link the license to the new hardware. Post-installation, you must update the OS to patch security vulnerabilities. While Windows Update handles OS patches, you …

8. Security Fundamentals

The Modern Threat Landscape A help desk ticket arrives: "User reports slow performance and encrypted file extensions on all documents in their shared network drive." You remote into the workstation and find a ransom note on the desktop demanding cryptocurrency for the decryption key. The user is the CFO. Security is no longer just an IT department problem; it is a business-critical priority. On the CompTIA A+ Core 2 (220-1102) exam, Security accounts for 25% of your grade. Because you already understand the underlying infrastructure from our chapters on Networking Fundamentals and Operating Systems Installation & Management, we can bypass the basics and focus directly on identifying threats, securing access, and hardening systems. Malware Identification and Mitigation Malware (malicious software) comes in many variants, each with distinct behaviors. The exam will test your ability to match a malware type to its symptoms and recommend the appropriate removal or mitigation strategy. Viruses and Worms A virus attaches itself to a clean file and requires a host program to execute. It activates when the user runs the infected file. A worm, on the other hand, is standalone malware that replicates itself to spread across networks without user intervention. Because worms do not need a host file, they can rapidly consume network bandwidth—a concept tied directly to your Networking Fundamentals knowledge. Ransomware Ransomware is currently the most destructive malware category. It encrypts user files or entire hard drives, demanding payment for the decryption key. Symptoms: Files have unknown extensions (e.g., .locked, .crypto), ransom notes appear on desktops, and users are locked out of their systems. Mitigation: Isolate the infected machine immediately to prevent lateral movement. Do not pay the ransom. Restore from offline, verified backups. Spyware and Rootkits Spyware operates covertly in the background, tracking user activity (keystrokes, browsing habits) and sending this data to an attacker. Keyloggers are a specific type of spyware that records every keystroke to capture passwords and credit card numbers. A rootkit is a particularly insidious form of malware that burrows deep into the operating system kernel or firmware. Symptoms: A rootkit grants attackers administrative-level control while actively hiding its existence from standard OS processes and Task Manager. Mitigation: Because rootkits intercept OS calls, standard antivirus software often cannot detect them. Removal typically requires booting into a clean environment (like Windows Preinstallation Environment) using offline scanning tools, or in severe cases, reimaging the machine. Trojans and PUPs A Trojan disguises itself as legitimate software. Unlike viruses, Trojans do not self-replicate; they rely on social engineering to trick users into installing them. Once installed, they often create a backdoor for attackers. PUPs (Potentially Unwanted Programs), while not always malicious, bog down system resources, alter browser settings, or serve ads. …

9. Software Troubleshooting

A user submits a help desk ticket: "My computer is acting weird." That phrase can mean anything from a minor annoyance to a catastrophic system failure. As an IT support technician, your job is to translate vague user complaints into specific technical diagnoses and apply the correct fixes. Software Troubleshooting accounts for 22% of your Core 2 (220-1102) exam. Building on the OS management principles from Chapter 7 and the security concepts from Chapter 8, this module focuses on diagnosing and resolving operating system failures, application crashes, malware infections, mobile OS issues, and data recovery scenarios. Troubleshooting Windows OS Problems Windows is the most prevalent desktop OS in enterprise environments, making its failures a primary focus for the CompTIA A+ exam. You must be prepared to diagnose systems that refuse to boot, crash unexpectedly, or slow to a crawl. Boot Failures and Recovery When a Windows machine fails to boot, the first step is to determine if the issue is hardware or software related. Refer to your Hardware & Network Troubleshooting knowledge if you hear beep codes or see POST failures. If the system passes POST but fails to load Windows, the issue resides in the boot partition, the Boot Configuration Data (BCD), or critical system files. Windows relies on the Windows RE (Recovery Environment), typically accessible via the Advanced Startup Options menu. To access this, interrupt the normal boot process three times (by holding the power button during boot) or boot from installation media. Key tools within Windows RE include: Startup Repair: An automated tool that scans for and fixes common boot issues, such as corrupted BCD files or missing boot sectors. System Restore: Reverts the system state, registry, and drivers to a previous restore point without affecting user data. System Image Recovery: Overwrites the entire drive with a previously captured system image. Command Prompt: Allows manual intervention. You will likely use bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd to manually reconstruct the boot partition data. If the system boots but missing OS files are causing instability, use the Deployment Image Servicing and Management (DISM) tool and System File Checker (SFC). Run DISM first to repair the Windows image, then run SFC to scan and replace corrupted system files using the healthy image. The commands are DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow. Blue Screen of Death (BSOD) A BSOD (officially known as a Stop Error) occurs when Windows encounters a critical error from which it cannot safely recover, such as a kernel-level driver failure or hardware incompatibility. When troubleshooting a BSOD: 1. Note the error code: The screen displays a hexadecimal stop code (e.g., 0x0000007B or IRQLNOTLESSOREQUAL). This code points you toward the general cause. 2. Isolate …

10. Operational Procedures & Professionalism

Safety First: Protecting Yourself, the Equipment, and the Environment You arrive at a client site to replace a failed network switch in a cramped IDF (Intermediate Distribution Frame) closet. The replacement switch weighs 35 pounds, the floor is slick from recent cleaning, and the rack rails are partially obstructed. As you pull the old switch out, it slips. You catch it awkwardly, twisting your lower back. You finish the job, but the next morning you can barely get out of bed. Technical brilliance means nothing if you injure yourself, destroy expensive hardware, or violate environmental laws. The CompTIA A+ exam heavily tests your knowledge of physical safety, environmental controls, and the processes that govern daily IT operations. ESD Prevention Electrostatic discharge (ESD) occurs when two objects with different electrical potentials come into contact, resulting in a sudden flow of electricity between them. While a static shock might only sting your finger, it carries enough voltage to permanently destroy sensitive microprocessors, RAM modules, and motherboard chipsets. To prevent ESD damage when handling internal components (as discussed in PC Hardware Components & Peripherals), follow these strict protocols: - Self-Grounding: If you don't have an ESD wrist strap available, touch an unpainted, grounded metal surface on the computer chassis before handling components. This equalizes your electrical potential with the case. - ESD Wrist Straps: Always wear an ESD wrist strap clipped to a grounded surface or the chassis. Never clip a wrist strap to a power supply that is plugged into a wall outlet. - ESD Mats: Use antistatic mats on your workbench and on the floor beneath your chair. Connect the mat to a ground plug. - Component Handling: Hold expansion cards and RAM strictly by their edges. Avoid touching the gold pins, capacitors, or exposed microchips. - Storage and Transport: Never lay sensitive components on plastic, foam, or carpet. Store and transport them inside antistatic bags (the silvery, metallic bags components ship in) or rigid antistatic containers. - Environmental Controls: ESD is exacerbated by low humidity. Maintain an environmental humidity level between 40% and 60% to reduce static buildup. Safe Lifting Techniques Hardware fails, and when it does, someone has to physically move it. Servers, large Uninterruptible Power Supplies (UPS), and high-density network switches are exceptionally heavy. Improper lifting is a leading cause of workplace injuries in IT. - Assess the Load: Before lifting, test the weight of the object. If it weighs more than 50 lbs (approx. 23 kg), or if it is awkwardly shaped, do not lift it alone. Get a partner or use a mechanical aid like a cart or pallet jack. - Proper Posture: Stand close to the object with your feet shoulder-width apart. - Lift with …

Continue learning