Loading course title...

Loading assessment title...

Connecting to LMS... Progress: in progress

Assessment

1. What is the main goal of system hardening? A. Make systems impossible to use B. Remove all monitoring C. Reduce unnecessary risk while keeping required functions reliable D. Avoid documentation

2. What should come early in a system hardening effort? A. Inventory systems, owners, roles, and classifications B. Delete all records C. Disable backups D. Assume every endpoint is already secure

3. What is a secure baseline? A. A random one-time change B. A list of unsupported software C. A way to avoid configuration review D. An approved expected configuration for a class of systems

4. What does reducing local attack surface usually involve? A. Installing every available tool B. Removing or restricting unnecessary services, software, accounts, and exposure C. Creating unused administrator accounts D. Turning off all logs

5. What is a good practice for privilege management? A. Give every user local administrator rights B. Use shared administrator accounts everywhere C. Use least privilege and review administrative access D. Never monitor privileged activity

6. Why are patching and endpoint protection important? A. They make ownership unnecessary B. They replace backups forever C. They only matter on test systems D. They reduce known risk and improve detection or response

7. Why should backups be tested? A. To confirm recovery is actually possible B. To avoid logging C. To remove rollback plans D. To make change control unnecessary

8. Which is the best system hardening operating routine? A. Guess, change production, and hope B. Inventory, baseline, reduce exposure, control privilege, patch, monitor, validate, and improve C. Disable logs and remove backups D. Make every exception permanent