An administrator is planning to use FortiDevSec to detect vulnerabilities in container images and is researching any platform limitations that they must take into account when using that tool. What…

Question

Options

• AIt does not support scanning private images that require Docker login.
• BIt is limited to dynamic application testing of container images.
• CIt focuses on scanning for encrypted secrets in containerized applications.
• DIt can detect vulnerabilities in containerized applications in Amazon Web Services (AWS)

• A
  95% (20)
• B
  5% (1)

Explanation

Option A is correct because FortiDevSec's container image scanning relies on pulling images locally to analyze them, and this process does not support authenticated Docker registry workflows - meaning images stored in private registries that require docker login cannot be scanned.

Why the distractors are wrong:

• B is incorrect because FortiDevSec performs static analysis (SAST) on container images, not dynamic application testing (DAST). Dynamic testing runs live applications, which is a different process entirely.
• C is incorrect because while FortiDevSec does include secret scanning, it is not focused solely on encrypted secrets - it covers a broad range of vulnerabilities including CVEs, misconfigurations, and dependency issues.
• D is a distractor phrased to sound like a limitation but is actually a capability, not a limitation. FortiDevSec can detect vulnerabilities in AWS-hosted containerized applications.

Memory tip: Think of the limitation as a "login gate" - FortiDevSec can scan what it can freely pull, but it can't knock on a private door (private registries requiring authentication). If your image is behind a login wall, FortiDevSec can't get in.

No community discussion yet for this question.