Containers offer a lightweight alternative to virtual machines by sharing the host OS's kernel. What is a key security practice for containers?

Question

Options

• ARunning containers with default settings
• BUsing containers to run multiple different applications on a single host
• CRegularly scanning containers and images for vulnerabilities
• DEnsuring containers use as much host resource as possible

• A
  2% (1)
• B
  6% (4)
• C
  87% (54)
• D
  5% (3)

Explanation

Regularly scanning containers and images for vulnerabilities (C) is essential because containers package application code alongside dependencies, and any embedded library or base image can harbor known CVEs - scanning catches these before they reach production. A is wrong because default settings often run containers as root and leave unnecessary capabilities enabled, violating the principle of least privilege. B is wrong because running multiple apps on a single host is a feature of containers, not a security practice - it actually increases the blast radius if one container is compromised. D is wrong because resource over-consumption (no CPU/memory limits) enables denial-of-service scenarios, both accidental and malicious; containers should be resource-constrained, not unconstrained.

Memory tip: Think "scan before you ship" - just as you'd run antivirus before deploying software, you scan container images before deploying them. The word regularly in option C is the giveaway that it's an ongoing security discipline, not a one-time setup step.

No community discussion yet for this question.