Which container scan is constructed correctly?

The correct answer is C. twistcli images scan -u api -p api --address https://us-west1.cloud.twistlock.com/us-3-123456789 --. The correct twistcli syntax for scanning a container image requires: the subcommand images scan, credentials via -u (username) and -p (password), the Console address via --address (pointing to the Prisma Cloud Compute Console URL), and finally the image name/tag to scan. Option…

Container Security

Question

Options

Atwistcli images scan -u api -p api --address https://us-west1.cloud.twistlock.com/us-3-123456789 --
Btwistcli images scan --docker-address https://us-west1.cloud.twistlock.com/us-3-123456789
Ctwistcli images scan -u api -p api --address https://us-west1.cloud.twistlock.com/us-3-123456789 --
Dtwistcli images scan -u api -p api --docker-address https://us-west1.cloud.twistlock.com/us-3-

How the community answered

(35 responses)

A
6% (2)
B
3% (1)
C
89% (31)
D
3% (1)

Explanation

The correct twistcli syntax for scanning a container image requires: the subcommand images scan, credentials via -u (username) and -p (password), the Console address via --address (pointing to the Prisma Cloud Compute Console URL), and finally the image name/tag to scan. Option B is wrong because it omits credentials and incorrectly uses --docker-address (which points to the Docker daemon, not the Console). Option D incorrectly uses --docker-address in place of --address for the Console endpoint. Option A is structurally similar to C but contains a syntax error in the choices as presented.

Topics

#Prisma Cloud CLI#Container Image Scanning#Vulnerability Management#CLI Authentication

Community Discussion

No community discussion yet for this question.

Full PCCSE Practice