Patch Management for Containerized Environments

Final Quiz

Connecting to LMS... Progress: in progress

Assessment

1. How are container vulnerabilities commonly remediated? A. By rebuilding and redeploying updated images B. By manually editing each running container C. By ignoring base images D. By disabling vulnerability management

2. Why do base images matter for patch management? A. Base images never contain vulnerable software B. Application images may inherit packages and vulnerabilities from their bases C. Base images are unrelated to container builds D. Base images replace application testing

3. Why can one vulnerability appear in many images? A. Each vulnerability affects only one artifact B. Registries remove duplicates automatically C. Multiple images may share the same base image or dependency D. Containers cannot share software ancestry

4. What does image scanning help identify? A. Office furniture B. Marketing plans C. Payroll deductions D. Potentially vulnerable packages and components inside images

5. What is an SBOM used for? A. Recording the software components and relationships in an artifact B. Replacing every vulnerability database C. Guaranteeing every component is secure D. Managing office inventory

6. Why is prioritization important in container patching? A. Every finding always has identical risk B. It directs remediation toward the greatest current real-world risk C. It replaces remediation D. It eliminates testing

7. Which factor can increase patch urgency? A. A confirmed false positive B. A private image that was never built or deployed C. Known exploitation or internet exposure D. A current mitigating control that removes all affected exposure

8. What should happen after an image dependency is updated? A. The image should bypass every test B. Production containers should be edited manually C. The original finding should be deleted immediately D. The image should be rebuilt, tested, promoted, redeployed, and verified

9. Why are rollback plans important? A. They help recover when a patched deployment causes problems B. They replace testing C. They eliminate every deployment risk D. They remove monitoring requirements

10. How can CI/CD support container patch management? A. By removing every approval and policy B. By automating builds, scans, tests, policy checks, signing, and promotion C. By disabling scanning D. By preventing image rebuilds

11. What is a policy gate? A. A payroll system B. A network cable C. A pipeline control enforcing requirements before promotion or deployment D. A marketing approval form

12. Why do Kubernetes nodes matter for patch management? A. Nodes are unrelated to containers B. Nodes never require updates C. Nodes replace image patching D. Workloads depend on node operating systems, runtimes, and Kubernetes components

13. What is a rolling update? A. A deployment approach that replaces workload instances gradually B. A manual edit inside a running container C. A method for ignoring vulnerabilities D. A way to remove monitoring

14. What is risk acceptance? A. Ignoring vulnerabilities without ownership B. A documented decision to tolerate residual risk under defined conditions C. Deleting remediation evidence D. Skipping governance

15. Which statement best summarizes patch management for containerized environments? A. It is manual editing of running containers B. It eliminates all vulnerabilities forever C. It is a controlled rebuild, test, redeploy, verify, and governance process D. It does not require ownership or testing