Question

Difficulty: Very hardApplication Installation and Configuration Concepts

A systems administrator is developing a standardized automated script to deploy a legacy line-of-business application across a enterprise network of 64-bit Windows workstations. Place the following installation and configuration steps in the correct chronological order from first to last.

  1. 1Verify 64-bit OS compatibility and install required 32-bit runtime environment libraries (WOW64 prerequisites).
  2. 2Execute the application installer package using an elevated administrative security token.
  3. 3Pass silent installation switches (e.g., /qn or /quiet) to suppress GUI prompts and user interaction during deployment.
  4. 4Apply system-wide configuration settings by updating application keys in HKEY_LOCAL_MACHINE.
  5. 5Configure folder-level NTFS permissions to enforce least privilege for standard domain users.

Answer

The correct sequence for automated application deployment is: 1) Verify architecture compatibility and install prerequisite runtimes, 2) Execute installer with elevated admin privileges, 3) Pass silent switches for unattended setup, 4) Modify global registry keys in HKLM for baseline config, and 5) Restrict NTFS folder permissions to enforce least privilege.
The correct order follows the standard technical workflow for automated software deployment: first, ensure environment dependencies and runtime compatibility (32-bit runtimes on 64-bit OS via WOW64); second, launch the installer with elevated administrative rights to ensure write access to protected areas; third, include silent command-line switches to suppress interactive prompts; fourth, write post-installation configurations to global registry locations; and finally, harden the target folder with proper NTFS least-privilege permissions.

Step-by-Step Solution

1
Audit architecture requirements and deploy runtime dependencies
System meets software dependencies and includes necessary 32-bit runtime support (WOW64).
Installers will fail immediately or produce runtime errors if required supporting libraries are absent prior to execution.
2
Invoke installer with administrative rights
Installer process runs under an elevated token.
Writing to protected areas like C:\Program Files (x86) and system registry hives requires administrative authorization.
3
Apply unattended command-line parameters
Installation runs silently without requiring interactive user input.
Automated deployment pipelines require silent switches to prevent setup wizard prompts from blocking automated script execution.
4
Configure global registry keys post-install
Application default settings are established under HKEY_LOCAL_MACHINE.
Post-installation settings depend on the application registry structure being populated by the installer first.
5
Enforce security permissions on binaries
Standard users are restricted to Read & Execute NTFS permissions on the installation directory.
Hardening software directory permissions must take place after all binaries and config files have been created.

Key Concept

Application Installation and Configuration Concepts
Estimated Time:3m 0s
Rate this question