Examkin

Question

Difficulty: Very hardApplication Installation and Configuration Concepts

A desktop support technician is deploying a legacy accounting application onto several newly imaged 64-bit Windows 11 Pro workstations. When standard domain users attempt to launch the application, it crashes immediately with an initialization error. The technician notes that the application runs properly only when launched by a local administrator using elevated privileges. Further investigation reveals that the application attempts to write temporary runtime state data to its install folder located at `C:\Program Files (x86)\VendorApp\Temp\`. The company security policy strictly forbids granting administrator rights or full control permissions over system directories to standard users. Which of the following actions is the BEST long-term solution to resolve this issue while maintaining security compliance?

  1. Reconfigure the application configuration settings or environment variables to redirect temporary data writes to `%LocalAppData%\VendorApp\Temp\`.Answer
  2. B
    Configure the application shortcut to execute with Compatibility Mode enabled for Windows 7 and select 'Run this program as an administrator'.
  3. C
    Upgrade the workstations to Windows 11 Enterprise and configure an AppLocker rule to bypass user account control for the application binary.
  4. D
    Run `icacls "C:\Program Files (x86)\VendorApp" /grant Users:(F) /T` from an elevated command prompt to grant standard users complete access.

Answer

Reconfigure the application configuration settings or environment variables to redirect temporary data writes to `%LocalAppData%\VendorApp\Temp\`.
Redirecting the application's temporary working directory to `%LocalAppData%` solves the permissions issue cleanly. Standard Windows accounts have full read/write privileges within their user profiles (`C:\Users\<username>\AppData\Local`), allowing the application to function without modifying default security settings on protected system folders like `Program Files (x86)` or giving administrative privileges to standard users.

Step-by-Step Solution

1
Analyze the cause of the application crash
Identified that standard domain users lack write permissions to `C:\Program Files (x86)\VendorApp\Temp\` under default Windows security architecture.
Protected system folders like `Program Files` and `Program Files (x86)` restrict write access to administrators to prevent unauthorized file modification and malware persistence.
2
Evaluate compliance and security constraints
Options granting administrator rights or broad NTFS write permissions to `Program Files (x86)` are rejected due to corporate least privilege enforcement.
Security best practices mandate that standard users should only have write permissions within their user profile directory.
3
Determine the proper architectural remediation
Redirecting application temporary storage to `%LocalAppData%` resolves permission conflicts natively within the user profile context.
Standard users inherently possess read/write permissions to their `%LocalAppData%` directory, eliminating the need for UAC elevation or over-privileged ACL modifications.

Key Concept

Application Installation and Permissions Architecture
Estimated Time:2m 0s
Rate this question

Topics

Application Installation and Configuration Concepts

More questions from this topic