Examkin

Question

Difficulty: HardWindows Security Settings and User Account Control

An IT technician is troubleshooting an older 32-bit custom accounting application on a Windows 11 Enterprise workstation. When standard users run the application, it appears to function normally and save configuration changes, but these changes are invisible to other users on the same machine. When an administrator logs in and runs the application, the application fails to load those user settings. What Windows User Account Control (UAC) feature is responsible for this behavior?

  1. UAC file and registry virtualization, which redirects writes from protected directories to %LocalAppData%\VirtualStore for standard user accounts.Answer
  2. B
    Explicit NTFS permission inheritance, which automatically elevates standard user permissions to full control when writing to Program Files.
  3. C
    64-bit architecture execution control, which prevents 32-bit applications from writing to the system registry unless compatibility mode is enabled.
  4. D
    Credential Manager domain synchronization, which stores application configuration files in encrypted user vaults rather than local disk drives.

Answer

UAC file and registry virtualization redirects write operations from protected system directories to a per-user VirtualStore directory when non-administrative accounts run legacy 32-bit applications.
The correct answer correctly identifies UAC file and registry virtualization. To maintain compatibility with older 32-bit applications that expect write access to system folders (such as C:\Program Files) or system registry hives (HKLM\Software), UAC silently redirects standard user write attempts to %LocalAppData%\VirtualStore. This allows the application to function without triggering access denied errors, but isolates the saved data to that specific standard user profile.

Step-by-Step Solution

1
Analyze the application behavior described in the scenario.
Standard users can save settings without error, but settings are isolated per user and not visible globally or to administrators.
This behavior indicates that file writes intended for shared system locations (e.g., C:\Program Files) are being redirected to user-specific locations.
2
Identify the Windows security mechanism responsible for backwards compatibility with legacy applications.
User Account Control (UAC) includes File and Registry Virtualization.
Legacy 32-bit applications without a requestedExecutionLevel manifest write to %LocalAppData%\VirtualStore instead of failing due to denied access to protected system paths.
3
Evaluate why administrators do not see these settings.
Administrative accounts bypass UAC virtualization and write directly to protected global directories.
Since the administrator writes to C:\Program Files directly, changes saved in a standard user's %LocalAppData%\VirtualStore are not read during administrative execution.

Key Concept

UAC File and Registry Virtualization
Rate this question

Topics

Windows Security Settings and User Account Control

More questions from this topic