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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Developer Exam - Topic 3 Question 94 Discussion

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 image3. 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?
B) Enable the Container Scanning API in Artifact Registry, and scan the built container images for vulnerabilities.
A) Enable Binary Authorization, and configure it to attest that no vulnerabilities exist in a container image.
C) Upload the built container images to your Docker Hub instance, and scan them for vulnerabilities.
D) Add Artifact Registry to your Aqua Security instance, and scan the built container images for vulnerabilities

Google Professional Cloud Developer Exam - 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

by Aide at Sep 18, 2024, 10:00 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Rose
9 months ago
D sounds interesting, but is it really necessary to add Aqua Security?
upvoted 0 times
...
Dallas
9 months ago
Wait, can we really trust the scans? I've heard mixed reviews.
upvoted 0 times
...
Cheryl
10 months ago
C doesn't make sense, why use Docker Hub when we have Artifact Registry?
upvoted 0 times
...
Renay
10 months ago
I disagree, A seems more secure with Binary Authorization.
upvoted 0 times
...
Mozell
10 months ago
B is the way to go! Container Scanning API is super handy.
upvoted 0 times
...
Carol
10 months ago
Uploading to Docker Hub feels like an unnecessary step; I think we should stick to Artifact Registry for scanning.
upvoted 0 times
...
Rosita
11 months ago
I practiced a similar question where we had to choose between different scanning options, and I think the Container Scanning API was the best choice there too.
upvoted 0 times
...
Isreal
11 months ago
I'm not entirely sure, but I think enabling Binary Authorization might be overkill for just scanning images.
upvoted 0 times
...
Sonia
11 months ago
I remember reading about the Container Scanning API in Artifact Registry; it seems like a straightforward way to scan for vulnerabilities.
upvoted 0 times
...
Justa
11 months ago
This seems straightforward enough. I think Option B is the way to go - it's the most direct solution that integrates with the existing Artifact Registry and shouldn't require major changes to the pipeline. I'm feeling pretty confident about this one.
upvoted 0 times
...
Ernest
11 months ago
Okay, I've got a strategy here. Since the question mentions minimizing changes that could disrupt other teams, I'm leaning towards Option B - enabling the Container Scanning API in Artifact Registry. That way, I can scan the images without having to change the existing pipeline or integrate with a third-party tool.
upvoted 0 times
...
Sharika
11 months ago
Hmm, I'm a bit unsure about this one. There are a few options presented, and I'm not sure which one would be the best fit. I'll need to think through the pros and cons of each approach.
upvoted 0 times
...
Marti
11 months ago
This looks like a straightforward question about implementing a vulnerability scan in a Cloud Build pipeline. I think the key is to find a solution that integrates well with the existing setup and doesn't disrupt other teams.
upvoted 0 times
...
Kimbery
11 months ago
Leveraged finance? Private banking? I'm not sure how those would fit the definition of facilitating direct lending. I think I need to re-read the question and options more closely to figure this out.
upvoted 0 times
...
Jerlene
2 years ago
Option D - adding Aqua Security? That's a bit excessive, don't you think? Gotta keep it simple.
upvoted 0 times
Elly
2 years ago
Option D - adding Aqua Security? That's a bit excessive, don't you think? Gotta keep it simple.
upvoted 0 times
...
Hildegarde
2 years ago
B) Enable the Container Scanning API in Artifact Registry, and scan the built container images for vulnerabilities.
upvoted 0 times
...
Lyndia
2 years ago
A) Enable Binary Authorization, and configure it to attest that no vulnerabilities exist in a container image.
upvoted 0 times
...
...
Carissa
2 years ago
Haha, uploading to Docker Hub just to scan? That's like taking the long way around!
upvoted 0 times
...
Michell
2 years ago
I like how Option B integrates the scanning right into the existing workflow. Keeps everything in one place.
upvoted 0 times
Jade
2 years ago
C) Upload the built container images to your Docker Hub instance, and scan them for vulnerabilities.
upvoted 0 times
...
Yolande
2 years ago
B) Enable the Container Scanning API in Artifact Registry, and scan the built container images for vulnerabilities.
upvoted 0 times
...
Joana
2 years ago
A) Enable Binary Authorization, and configure it to attest that no vulnerabilities exist in a container image.
upvoted 0 times
...
...
Novella
2 years 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
2 years 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
2 years 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
Gennie
2 years ago
Adding this step will ensure that any vulnerabilities are caught early on and can be addressed before deployment.
upvoted 0 times
...
Daniel
2 years ago
It's important to prioritize security measures like vulnerability scanning in the build process.
upvoted 0 times
...
Rodrigo
2 years ago
Enabling the Container Scanning API in Artifact Registry will definitely help with keeping the deployment pipeline secure.
upvoted 0 times
...
Erick
2 years ago
I agree, Option B is the most efficient choice for scanning the container images.
upvoted 0 times
...
...
Hyun
2 years 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
2 years 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