A systems administrator is troubleshooting a newly deployed enterprise graphics application on Windows 11 workstations. Standard domain users can launch the application, but it fails whenever the software attempts to save shared project templates to its default installation directory. Additionally, the application fails to load required 32-bit legacy automation add-ins. Which of the following actions should the administrator perform to resolve these operational issues while adhering to security best practices and architecture requirements? (Select TWO.)
- Relocate the shared project templates to the ProgramData directory and grant standard users Modify permissions to that folder.Answer
- Deploy the 32-bit edition of the host application instead of the 64-bit edition to match the add-in architecture.Answer
- CGrant standard user accounts membership in the local Administrators group to bypass file access restrictions.
- DUpgrade the workstations to Windows 11 Enterprise to enable 32-bit process emulation for 64-bit host applications.
Answer
The administrator should relocate the shared project templates to the ProgramData folder with appropriate user permissions and deploy the 32-bit version of the host application.
The correct options address both permission restrictions and process bitness requirements. Moving user-writable files to the ProgramData folder with modified ACLs allows standard users to save files without compromising system security. Furthermore, installing the 32-bit version of the main application ensures process-level architecture compatibility with 32-bit legacy add-ins.
Step-by-Step Solution
Key Concept
Application installation folder permissions and bitness/architecture compatibility requirements