Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Developer Topic 3 Question 94 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 94
Topic #: 3
[All Professional Cloud Developer Questions]

You are reviewing and updating your Cloud Build steps to adhere to Google-recommended practices. Currently, your build steps include:

1. Pull the source code from a source repository.

2. Build a container image

3. Upload the built image to Artifact Registry.

You need to add a step to perform a vulnerability scan of the built container image, and you want the results of the scan to be available to your deployment pipeline running in Google Cloud. You want to minimize changes that could disrupt other teams' processes What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Michell
3 days ago
I like how Option B integrates the scanning right into the existing workflow. Keeps everything in one place.
upvoted 0 times
...
Novella
6 days ago
I'm not sure about option B. I think enabling Binary Authorization (option A) could also be a good choice to attest that no vulnerabilities exist in the container image.
upvoted 0 times
...
Rueben
8 days ago
Hmm, I'm not sure Binary Authorization is the right fit for this use case. Seems like overkill just to check for vulnerabilities.
upvoted 0 times
...
Tresa
10 days ago
Option B seems like the best choice here. Scanning the images directly in Artifact Registry is a straightforward way to get the vulnerability results without disrupting other processes.
upvoted 0 times
...
Hyun
11 days ago
I agree with Isidra. Option B seems like the most efficient way to add a vulnerability scan step without disrupting other teams' processes.
upvoted 0 times
...
Isidra
14 days ago
I think option B is the best choice. Enabling the Container Scanning API in Artifact Registry will allow us to scan the built container images for vulnerabilities.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77