An IT technician is deploying a specialized line-of-business application on a newly installed Windows 11 workstation. The application requires elevated administrative rights to install, requires network access on a custom service port, and saves shared database cache files to a central local directory for standard users. What is the correct sequence of steps the technician should perform from first to last to complete this installation and post-installation configuration?
- 1Verify system prerequisite compatibility, including OS architecture (64-bit) and required library dependencies.
- 2Execute the application setup installer using elevated administrator privileges.
- 3Configure NTFS permissions on the application data folder in C:\ProgramData to grant standard users Modify permissions.
- 4Create custom inbound and outbound traffic rules in Windows Defender Firewall for the application's network port.
- 5Log in under a standard user account to test application launch, network connectivity, and data persistence.
Cevap
The correct sequence of steps is: 1) Verify system prerequisite compatibility, 2) Execute the application installer using elevated administrator privileges, 3) Configure NTFS permissions on the shared folder in C:\ProgramData, 4) Create custom inbound and outbound rules in Windows Defender Firewall, and 5) Log in under a standard user account to test functionality.
The correct deployment workflow follows established system administration standards: first verifying pre-installation system compatibility, then running the installer with elevated administrator rights to copy files to protected system locations. Following installation, post-install configurations are applied—adjusting NTFS permissions on shared directories (such as C:\ProgramData) so standard users can write data, and opening necessary network ports in Windows Defender Firewall. Finally, functional testing must occur under a standard user profile to confirm end-user operational capability.
Adım Adım Çözüm
Anahtar Kavram
Application installation lifecycle and post-installation security/permission configuration