BlackFriday 2024! 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:

Jerlene
24 days ago
Option D - adding Aqua Security? That's a bit excessive, don't you think? Gotta keep it simple.
upvoted 0 times
...
Carissa
28 days ago
Haha, uploading to Docker Hub just to scan? That's like taking the long way around!
upvoted 0 times
...
Michell
1 months ago
I like how Option B integrates the scanning right into the existing workflow. Keeps everything in one place.
upvoted 0 times
Jade
10 days ago
C) Upload the built container images to your Docker Hub instance, and scan them for vulnerabilities.
upvoted 0 times
...
Yolande
12 days ago
B) Enable the Container Scanning API in Artifact Registry, and scan the built container images for vulnerabilities.
upvoted 0 times
...
Joana
19 days ago
A) Enable Binary Authorization, and configure it to attest that no vulnerabilities exist in a container image.
upvoted 0 times
...
...
Novella
1 months 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
1 months 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
1 months 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
Rodrigo
2 days ago
Enabling the Container Scanning API in Artifact Registry will definitely help with keeping the deployment pipeline secure.
upvoted 0 times
...
Erick
25 days ago
I agree, Option B is the most efficient choice for scanning the container images.
upvoted 0 times
...
...
Hyun
1 months 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
1 months 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