Skip to main content
Revy's Tech Journey, powered by Revtek
Back to Study
A+ Core 2 · CompTIA 220-1202 V15 · Objective C2-1.10

Given a scenario, install applications according to requirements

Drill flashcardsFocused quizBrowse all objectives (sidebar view)

Objective 1.10: Given a scenario, install applications according to requirements

Cert: CompTIA A+ Core 2 (220-1202) V15 Domain: 1.0 Operating Systems Weight: Part of the 28% Operating Systems domain Depth: Given a scenario, install. The candidate must check requirements, pick distribution methods, evaluate impact, and complete the install.

What this objective tests

You should be able to verify a system meets an application's requirements (CPU, RAM, VRAM, GPU type, storage, OS compatibility, 32-bit vs 64-bit), pick the right distribution method (physical media, ISO, downloadable installer, image deployment), and predict the impact of the new app on the device, network, operations, and business.

Key facts

32-bit vs 64-bit dependent application requirements:

  • 32-bit apps run on both 32-bit and 64-bit Windows (via WOW64 compatibility layer on 64-bit).
  • 64-bit apps require 64-bit Windows; they won't install on 32-bit OS.
  • 32-bit apps can only address ~4 GB of memory (theoretical; practically less). For memory-heavy apps (video editing, CAD, large databases), 64-bit is required.
  • Modern Windows installs default to 64-bit; 32-bit Windows is rare on new hardware.

Dedicated vs integrated graphics card:

  • Integrated GPU: shares system RAM, lower performance, no extra cost or power draw. Fine for office work, video conferencing, web.
  • Dedicated GPU: separate card with its own VRAM and cooling, higher performance, more power. Required for 3D modeling, video editing, gaming, machine learning, some CAD apps.
  • Some apps list "discrete GPU required" or "OpenGL/DirectX 12 capable GPU" in their requirements.

VRAM (Video RAM) requirements:

  • Memory on the GPU itself. Holds textures, framebuffers, model data.
  • Video editing and 3D apps often have minimum and recommended VRAM (e.g., 4 GB minimum, 8+ GB recommended).
  • Integrated GPUs don't have dedicated VRAM; they carve out system RAM dynamically (shared memory).

RAM requirements:

  • Total system memory. Minimum (will run but slow) vs recommended (smooth operation).
  • For business apps, 16 GB is the modern baseline. Heavy workloads (video editing, virtualization, large datasets) need 32-64+ GB.

CPU requirements:

  • Specific CPU generation or feature requirements (e.g., "Intel 8th Gen or newer", "ARM64 supported", "AVX2 instruction set required").
  • Some apps require specific feature flags (AVX2, SSE4.2) which older CPUs lack.

External hardware tokens:

  • USB security keys or hardware dongles required by some specialty apps (CAD software historically, some compliance tools).
  • App won't run without the token plugged in.

Storage requirements:

  • Disk space needed for installation. Some apps list "additional space for working files" beyond the install footprint (video apps need scratch space, databases need data space).
  • SSD vs HDD: some apps require or strongly recommend SSD for performance (game launchers, modern dev tools).

Application to OS compatibility:

  • App must run on the target OS version and edition.
  • Some apps require Pro+ (use Hyper-V, BitLocker integration, etc.).
  • Some apps drop support for older Windows versions; check the vendor's supported OS matrix.

Physical media vs mountable ISO file:

  • Physical: DVD/USB shipped with the software. Less common in modern delivery.
  • ISO: disk image file. Mount in Windows (double-click in Windows 10/11) or burn to USB/DVD.
  • ISO is the standard for OS installers and many enterprise app installers.

Downloadable package:

  • Installer downloaded from the vendor website. Most consumer apps work this way.
  • Verify the download with a checksum or signed installer to avoid tampered builds.

Image deployment:

  • Apps pre-installed into a reference image, deployed to multiple PCs at once (covered in 1.2 install methods).
  • Common for line-of-business apps across an org's PC fleet.

Device impact:

  • New apps consume CPU/RAM/storage and may install drivers, services, or kernel extensions that run continuously.
  • Heavy apps (antivirus, RMM agents, sync clients) can slow older hardware noticeably.
  • Multiple competing AV/security agents can conflict and degrade performance.

Network impact:

  • Some apps generate significant network traffic (cloud sync, telemetry, large model downloads).
  • New apps may need firewall rules opened (inbound or outbound) on the local OS firewall or the corporate firewall.
  • Bandwidth-heavy apps (video conferencing, large file sync) at scale can saturate office connections.

Operation impact:

  • New apps change how users work. Plan training, change-management, support readiness.
  • Some apps require user account changes (new logins, MFA enrollment).

Business impact:

  • Licensing cost, ongoing subscription, vendor support agreements.
  • Compliance: some apps require specific certifications (HIPAA, SOC 2, FedRAMP) for regulated environments.
  • Risk assessment: data-handling apps need vetting before they touch sensitive data.

Common gotchas

  • Installing a 64-bit app on 32-bit Windows. Fails with "this app can't run on your PC." Verify OS architecture before quoting an upgrade.
  • Integrated GPU on a CAD workstation. App runs but performance is unusable. Check GPU requirements before quoting hardware.
  • Disk space "just barely enough." App installs, then fails during first use because temp / scratch / log space wasn't accounted for.
  • AV conflicts. Two real-time antivirus engines on the same Windows can fight each other; performance and stability both suffer. Only one real-time AV at a time.
  • Forgot driver. Hardware-dependent apps (capture software, specialty USB devices) need the device driver installed separately. Install fails or app crashes if missed.
  • License key entry missed. Trial install completes, vendor never receives the corporate license, app reverts to trial mode after 30 days.
  • Untrusted installer. Downloaded an installer that wasn't from the vendor's official site. Signature mismatch or no signature is a red flag; bundled malware is the risk.

Real-world context

Pre-install checklist that prevents most failed installs:

  1. Identify the app's documented requirements (vendor's system requirements page).
  2. Compare to the target PC's specs (System Information / About).
  3. Verify OS architecture (32 vs 64-bit) and edition (Home vs Pro).
  4. Verify the user has admin privileges or that a deployment system will run with elevation.
  5. Verify disk space, with headroom for working files.
  6. Verify GPU/VRAM if relevant.
  7. Plan AV exclusions if the app conflicts with security software.
  8. Verify license keys and activation servers are reachable from the target network.
  9. Test in a non-production environment first for new apps.
  10. Document the install (version, location, license, configuration) for future support.

Distribution method by scale:

  • 1 PC: download installer, install manually.
  • 5-50 PCs: build a silent install script or push via RMM tool (NinjaOne, Datto, Atera).
  • 50+ PCs: package via Intune, SCCM, or equivalent and deploy automatically.

Sources

  • [CompTIA A+ 220-1202 Exam Objectives Version 4.0, Section 1.10](../../../../../../30-RevyTechJourney/CompTIA%20A%2B%20220-1202%20Exam%20Objectives%20%284.0%29.pdf)
  • [Microsoft Learn: System requirements for Windows](https://www.microsoft.com/en-us/windows/windows-11-specifications)
  • [Microsoft Learn: Win32 application compatibility](https://learn.microsoft.com/en-us/windows/win32/)
  • [Wikipedia: WoW64](https://en.wikipedia.org/wiki/WoW64)