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 DevOps Engineer Exam - Topic 5 Question 57 Discussion

Your company is using HTTPS requests to trigger a public Cloud Run-hosted service accessible at the https://booking-engine-abcdef .a.run.app URL You need to give developers the ability to test the latest revisions of the service before the service is exposed to customers What should you do?
B) Runthegcioud run services update-traffic booking-engine ---to-revisions LATEST*! command Use the ht tps: //booking-engine-abcdef. a. run. ape URL for testing
A) Runthegcioud run deploy booking-engine ---no-traffic ----ag dev command Use the https://dev----booking-engine-abcdef. a. run. app URL for testing
C) Pass the curl -K 'Authorization: Hearer S(gclcud auth print-identity-token)' auth token Use the https: / /booking-engine-abcdef. a. run. app URL to test privately
D) Grant the roles/run. invoker role to the developers testing the booking-engine service Use the https: //booking-engine-abcdef. private. run. app URL for testing

Google Professional Cloud DevOps Engineer Exam - Topic 5 Question 57 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 57
Topic #: 5
[All Professional Cloud DevOps Engineer Questions]

Your company is using HTTPS requests to trigger a public Cloud Run-hosted service accessible at the https://booking-engine-abcdef .a.run.app URL You need to give developers the ability to test the latest revisions of the service before the service is exposed to customers What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

The best option for securing the CI/CD deployment pipeline is to configure vulnerability analysis with Artifact Registry and Binary Authorization. Vulnerability analysis is a feature that allows you to scan container images for known vulnerabilities and security issues. You can use vulnerability analysis with Artifact Registry, which is a service that allows you to store and manage container images and other artifacts. By using vulnerability analysis with Artifact Registry, you can ensure that your container images are scanned for vulnerabilities before they are deployed. Binary Authorization is a feature that allows you to enforce signature-based validation when deploying container images. You can use Binary Authorization with Cloud Build, which is a service that allows you to build and deploy container images. By using Binary Authorization with Cloud Build, you can ensure that only authorized and verified container images are deployed to your environment.


by Linn at Nov 22, 2023, 07:23 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Marguerita
9 months ago
C is interesting, but using curl for testing feels outdated.
upvoted 0 times
...
Marsha
9 months ago
Wait, are we sure about using the private URL in D? Sounds risky.
upvoted 0 times
...
Joanne
10 months ago
I think D could work too, but it seems more complicated.
upvoted 0 times
...
Javier
10 months ago
Totally agree, A makes the most sense!
upvoted 0 times
...
Joesph
10 months ago
A is the way to go for testing without affecting live traffic.
upvoted 0 times
...
Macy
10 months ago
Option D mentions granting roles, which seems important for access control, but I wonder if using a private URL is necessary for testing.
upvoted 0 times
...
Wynell
11 months ago
I feel like option C is about using curl with an auth token, but I’m not clear if that’s the best way to test without exposing it to customers.
upvoted 0 times
...
Loise
11 months ago
I'm not entirely sure, but I remember something about updating traffic to a specific revision. Option B might be related to that, but it seems risky to use the main URL for testing.
upvoted 0 times
...
Chantell
11 months ago
I think option A sounds familiar, using the `--no-traffic` flag to deploy without affecting the live service. That could work for testing.
upvoted 0 times
...
Matthew
11 months ago
Option D seems interesting, but I'm not sure about the private URL. Wouldn't it be better to use the public URL for testing, even if we need to grant additional permissions?
upvoted 0 times
...
Norah
11 months ago
I'm leaning towards option C. Using an auth token to test privately might be the safest way to ensure the latest changes don't impact customers.
upvoted 0 times
...
Gerald
11 months ago
Option B looks promising. Updating the traffic to the latest revision and using the main URL for testing would allow developers to test in a production-like environment.
upvoted 0 times
...
Sage
11 months ago
I'm a bit unsure about this one. The options all seem similar, but I'm not sure which one is the best approach. Maybe I should re-read the question carefully.
upvoted 0 times
...
Carol
11 months ago
I think option A is the way to go here. Deploying the latest revision without traffic and using the dev URL for testing seems like the cleanest approach.
upvoted 0 times
...
Darrel
11 months ago
I think I can handle this. The key is to follow the instructions step-by-step and make sure I have the RHEL system roles package installed first.
upvoted 0 times
...
Kallie
11 months ago
I remember practicing a similar question; I feel like Cisco Unified IP IVR might be a good option for cost-effectiveness, but I could be wrong.
upvoted 0 times
...
Rodney
11 months ago
I'm a bit confused by this question. The options all seem related to elicitation, but I'm not sure which one is the best answer. I'll need to review my notes on elicitation techniques to make a confident choice.
upvoted 0 times
...
Lemuel
11 months ago
I believe stateful firewalls do handle return traffic on their own sometimes, but I need to review that again; D seems off to me.
upvoted 0 times
...
Annamae
2 years ago
Hmm, I'm not sure about option C. Passing an auth token to test the service privately feels a bit clunky. And option D, using a private URL, might be too restrictive for the developers.
upvoted 0 times
Kaitlyn
2 years ago
A) Run the cloud run deploy booking-engine ---no-traffic ----ag dev command. Use the https://dev----booking-engine-abcdef. a. run. app URL for testing
upvoted 0 times
...
Anisha
2 years ago
B) Run the cloud run services update-traffic booking-engine ---to-revisions LATEST*! command. Use the https://booking-engine-abcdef. a. run. app URL for testing
upvoted 0 times
...
Nakita
2 years ago
A) Run the cloud run deploy booking-engine ---no-traffic ----ag dev command. Use the https://dev----booking-engine-abcdef. a. run. app URL for testing
upvoted 0 times
...
Misty
2 years ago
B) Run the cloud run services update-traffic booking-engine ---to-revisions LATEST*! command. Use the https://booking-engine-abcdef. a. run. app URL for testing
upvoted 0 times
...
Carin
2 years ago
A) Run the cloud run deploy booking-engine ---no-traffic ----ag dev command. Use the https://dev----booking-engine-abcdef. a. run. app URL for testing
upvoted 0 times
...
...
Yun
2 years ago
Yeah, that's a good point. Option B looks more promising - updating the traffic to use the latest revision. That way, everyone can test the latest version without disrupting the main service.
upvoted 0 times
...
Dawne
2 years ago
Okay, let's start with option A. Deploying the service with no traffic seems like it could work, but I'm not sure if the dev URL would be accessible to everyone who needs to test it.
upvoted 0 times
...
Evette
2 years ago
This is a tricky question, I'm not sure which answer is the best. Let's go through each option and see if we can figure it out.
upvoted 0 times
...

Save Cancel