Docker Security and Best Practices

Test how well you understand image security,user permissions,and vulnerability scanning.

1. What is the default user context in a Docker container when no user is explicitly specified?
2. Which of the following are considered best practices for securing Docker images?
3. Running a Docker container with the --privileged flag enhances security by restricting container capabilities.
4. What command is used to scan Docker images for vulnerabilities using Docker's official tool (integrated with Docker Scout)?
5. What is a primary benefit of configuring a Docker container with a read-only filesystem?
6. Which of these are Docker security features that restrict container capabilities?
7. Storing database passwords in a Docker image (e.g., via Dockerfile ENV) is a secure practice.
8. What Linux kernel feature is used by Docker to limit container resources like CPU, memory, and I/O?
9. Which Dockerfile directive explicitly sets the user context for the container to run as, reducing security risks?
10. To reduce the attack surface of Docker containers, which practices should be implemented?
11. Docker Content Trust (DCT) ensures the integrity and authenticity of Docker images using digital signatures.
12. What is the recommended method to securely manage sensitive data (e.g., API keys) in Docker containers?
13. What risk is primarily mitigated by using a non-root user in Docker containers?
14. Which practices enhance Docker daemon security?
15. Using the 'latest' tag for Docker images in production is recommended to ensure access to the newest security patches.
Answered 0 of 0 — 0 correct