Why might an image assessment fail to complete?

Question

Options

• ARuntime policy conflicts
• BIncorrect registry credentials or access scope
• CSensor group misassignment
• DFusion SOAR misconfiguration

• B
  93% (26)
• C
  4% (1)
• D
  4% (1)

Explanation

Accessing a container image registry requires valid credentials and sufficient permission scope - without them, the scanner cannot authenticate or retrieve the image, causing the assessment to fail before it can complete. Option B is correct because image assessment tools must pull images from registries (e.g., ECR, Docker Hub, GCR), and misconfigured credentials or a token with insufficient scope (e.g., missing read permissions on the target repository) will block that pull entirely.

Why the distractors are wrong:

• A (Runtime policy conflicts): Runtime policies govern behavior in running containers; they don't affect the static image scanning pipeline.
• C (Sensor group misassignment): Sensor groups organize hosts with installed sensors - a separate concern from registry-based image scanning, which doesn't rely on group assignment.
• D (Fusion SOAR misconfiguration): Fusion SOAR handles workflow automation and security orchestration; it has no role in authenticating to registries or completing image pulls.

Memory tip: "To assess, you need access." - If the scanner can't log in to the registry with the right credentials and scope, there's nothing to assess.

No community discussion yet for this question.