A number of employees report that parts of an ERP application are not working.
The systems administrator reviews the following information from one of the employee workstations: Execute permission denied: financemodule.dll Execute permission denied: generalledger.dll Which of the following should the administrator implement to BEST resolve this issue while minimizing risk and attack exposure?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
Based on the given information, it appears that the employees are facing an issue where they are unable to execute certain modules of the ERP application due to denied permission for two DLL files, "financemodule.dll" and "generalledger.dll". In order to resolve this issue while minimizing risk and attack exposure, the systems administrator should implement the following solution:
B. Verify the DLL's file integrity.
Explanation:
DLL (Dynamic Link Library) files contain executable code that can be shared among multiple applications. These files are usually stored in a shared location on a network or in the system's directory. The error message suggests that the application is unable to execute due to denied permission for two specific DLL files.
Verifying the DLL file integrity involves checking the file for any changes or modifications that may have occurred since it was last installed. This can help determine if the file has been tampered with or infected with malware.
To verify the DLL file integrity, the administrator can use a tool such as Microsoft's System File Checker (SFC). SFC scans the DLL files on the system and compares them to a known good version. If any inconsistencies or changes are detected, SFC can replace the corrupted or modified file with a clean copy from a backup or installation media.
Updating the application blacklist (option A) would not be effective in resolving this issue since the problem is with the DLL files and not the application itself. Whitelisting the affected libraries (option C) could be a potential solution, but it may not be practical since DLL files are often shared among multiple applications and whitelisting them could cause compatibility issues. Placing the affected employees in the local administrator's group (option D) would increase their privileges and could potentially expose the system to additional security risks.