Legacy Haven University

A technician who cannot match CPU cores, RAM channels, GPU class, storage interface, PSU wattage, and cooling to a workload fails the hardware scenario on CompTIA A+ Core 1 (220-1201). You size each part against the job: CAD needs maximum RAM and a workstation GPU, audio/video editing needs fast sequential storage plus a capture card and dual displays, and gaming needs a high-TDP GPU, strong 12V rail, and aggressive cooling.

CompTIA no longer lists “custom PC configuration” as its own numbered objective the way older A+ exams did. The same decisions now live inside Domain 3. You compare RAM characteristics (3.3), pick storage devices and RAID (3.4), install motherboards, CPUs, and add-on cards (3.5), and install the appropriate power supply (3.6). Performance-based questions still hand you a role—marketing clerk, game developer, video editor—and force you to drag the right CPU, memory kit, video card, and wattage onto the board. Study the official hardware map in the A+ Core 1 220-1201 exam hub so every part choice maps to an objective, not a vendor slogan.

How a Custom Build Decision Actually Works

You start with the workload, not the shopping cart. The CPU executes the application threads. More cores and a higher boost clock cut render time and compile time. The memory controller on that CPU feeds those cores. Dual-channel or quad-channel DIMMs raise bandwidth; ECC DIMMs catch bit flips on long CAD sessions. The GPU either rasterizes frames (gaming) or accelerates compute and viewport redraws (CAD/CAM). Storage either streams large media files in order (A/V) or serves many small random reads (game assets, project files). The PSU converts wall AC to the 12V rail that feeds the GPU and CPU. Cooling removes the heat those parts dump into the case.

If any one of those links is undersized, the system throttles. The GPU hits its power limit and drops clocks. The CPU waits on RAM. The NVMe queue saturates. The exam tests whether you see that chain before you pick parts.

CAD / CAM and Graphic Design Workstations

Computer-aided design (CAD) and computer-aided manufacturing (CAM) software—SolidWorks, AutoCAD, Revit, Fusion 360—keeps large 3D assemblies in RAM and redraws them on every orbit. Graphic design tools such as Photoshop and Illustrator do the same with layered raster and vector files.

Give this machine a multicore x86/x64 CPU with a high core count. Enable virtualization support in UEFI only if the designer also runs local VMs; most CAD seats do not need it. Install the maximum supported RAM in matched dual-channel or quad-channel DIMMs. Prefer ECC RAM when the board and CPU support it, because a single flipped bit in a 40-hour assembly file costs more than the DIMM premium.

Install a high-end video card in a full-length PCIe x16 slot. CAD vendors certify workstation GPUs (NVIDIA RTX Ada/Blackwell professional line, AMD Radeon Pro) more often than consumer gaming cards. Those cards expose more VRAM, better FP64/viewport drivers, and certified ISV support. Pair the card with a display that has a wide color gamut, high pixel density, and an IPS or Mini-LED panel so line weights stay accurate.

Put the OS and active project files on NVMe (M.2 PCIe). Archive libraries can live on a large SATA SSD or a RAID 1 pair. Size the PSU for the GPU’s peak plus CPU TDP plus a 20–30 percent headroom margin. Use an ATX board so you have enough PCIe slots and DIMM banks. Liquid or high-static-pressure air cooling keeps the CPU out of thermal throttle during rebuilds.

Exam trap: a cheap consumer GPU with 8 GB of VRAM looks fine until the model exceeds VRAM and the viewport stutters. CompTIA’s “high-end video” language means certified workstation silicon and enough VRAM for the scene, not the cheapest card with an HDMI port.

Audio and Video Editing Workstations

An audio/video (A/V) editor cuts multi-cam timelines, grades color, and mixes stems. The bottleneck is sequential throughput and real-time decode, not peak frame rate.

Choose a multicore CPU with strong single-thread boost for effects that still refuse to scale. Load the board with a large non-ECC DIMM kit; editing suites cache frames and waveforms in RAM. Add a dedicated sound card or a quality USB audio interface when the onboard codec introduces latency or noise. Add a capture card when the editor ingests HDMI or SDI from cameras and switchers.

Storage is the part most candidates under-spec. Put scratch disks and active timelines on NVMe. Keep a second fast SSD for media cache. Park finished exports and camera archives on a high-capacity HDD or a RAID 5/10 array if the shop needs redundancy. RAID 0 raises sequential speed but dies on a single disk failure—do not use it as the only copy of client media.

Give the editor at least two displays: one for the timeline, one for the program monitor. Use DisplayPort or HDMI; match refresh rate and color gamut to the delivery spec. Size the PSU for the GPU (colorists still need a capable video card for accelerated encode and scopes) and for any capture hardware. An ATX or microATX board is fine; you need PCIe slots for the capture card and GPU, not a compact ITX layout that starves expansion.

Exam trap: “dual monitors” is not decoration. CompTIA still treats a second display as a required A/V trait. A single 4K panel does not replace a timeline-plus-preview layout in the scenario language.

Gaming PCs

A gaming PC pushes a GPU as close to its boost clock as power and thermals allow. Frame time, not spreadsheet fidelity, is the metric.

Install a high-core, high-boost CPU so the game thread and background processes do not stall the GPU. Pair it with fast dual-channel DDR5 (or the current DDR iteration the board requires). Capacity matters less than in CAD; 32 GB covers current titles, 64 GB covers streaming-plus-game plus future headroom.

The video card is the budget center. It must occupy a PCIe x16 slot, draw from dedicated 12V GPU power connectors, and dump heat through a thick cooler. That heat forces the rest of the build: a high-wattage PSU with a strong single 12V rail, a modular cable set so airflow stays clean, and case fans or a liquid loop that keep GPU junction temperature under the throttle point. Enable XMP/EXPO in UEFI so the RAM actually runs at the advertised rate.

Put the OS and current games on NVMe. A second SATA SSD holds the library. RAID is optional; gamers rarely trade capacity for redundancy. Add a discrete sound card only when the player uses studio headphones or a DAC; onboard audio is enough for most exam scenarios.

Cooling is not optional on this build. High-TDP CPUs and GPUs require a capable air cooler or AIO, fresh thermal paste, and unobstructed intake. UEFI fan curves and temperature monitoring (objective 3.5) let you prove the system stays in spec under load.

Exam trap: a 450 W PSU behind a 350 W GPU fails the 3.6 wattage-rating check even if the machine posts. Add CPU, drives, fans, and 20–30 percent overhead before you pick the label on the box.

Component Matrix You Should Memorize

Read that table left to right the way a PBQ does. The marketing manager who only runs Office and a browser gets onboard graphics, a modest PSU, and no capture card. The game developer who drives three monitors and graphics-intensive tools gets the high-end GPU and the 750–1000 W supply. CompTIA will mix those two seats on one screen and expect you to keep costs down where the role does not justify silicon.

Motherboard, Firmware, and Power Details That Change the Build

Form factor is a constraint, not a style choice. ATX gives you more PCIe slots, more DIMM banks, and better airflow for long GPUs. microATX cuts cost and case size but may drop a slot you need for a capture card. ITX forces a short GPU, fewer DIMMs, and a SFX or compact PSU—fine for a silent editor station, wrong for a triple-slot workstation card.

Match the CPU socket to the vendor: Intel and AMD use different sockets and chipset families. Confirm the board’s QVL for the exact DIMM kit. Enable the features the workload needs in UEFI: virtualization support for a CAD box that also hosts labs, Secure Boot and TPM for a shop that images Windows, temperature monitoring and fan curves for any high-TDP build. Leave unused options off so the firmware surface stays small.

On the PSU, read the 12V rail current, not only the total wattage sticker. GPUs and CPUs pull from 12V. Confirm input voltage (110–120 VAC vs. 220–240 VAC) for the site. Prefer modular cables so unused leads do not block intake. Energy-efficiency ratings (80 Plus and successors) cut heat inside the case; they do not replace correct wattage. Redundant PSUs belong in servers, not these three desktops, unless the scenario is a small render node that cannot go down mid-job.

What CompTIA Will Put in Front of You

Expect a drag-and-drop or matching item that names a role and a short list of tasks. You will see mixed parts: an ARM board next to an x86-64 i7, onboard graphics next to a high-end card, 450 W next to 1000 W. Discard anything that breaks compatibility first (wrong socket, SODIMM in a desktop, ARM for a Windows x64 workstation). Then discard anything that overspends against the role. Then meet the hard requirements: extra monitors for the developer, VRAM and RAM for the CAD seat, NVMe for the editor’s scratch disk.

When you review, say the workload out loud, then name the bottleneck: viewport (GPU + RAM), timeline (NVMe + RAM), frames (GPU + 12V + cooling). That sentence is the entire custom-configuration topic, rewritten in 220-1201 language.