MENU
You are deploying a Python application to Cloud Run using Cloud Build. The Cloud Build pipeline is shown below:
You want to optimize deployment times and avoid unnecessary steps What should you do?
Suggested Answer: B
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
ST
Stefany
11 months ago
Wait, can you really skip pushing to Artifact Registry? That sounds too good to be true!
LE
Leeann
11 months ago
I disagree with D, seems like overkill for most projects.
YV
Yvonne
11 months ago
Storing images in the same region makes sense, option C is solid.
HE
Helaine
11 months ago
Removing the push step? That sounds risky!
ED
Edna
12 months ago
I think option B is the best choice for caching.
LE
Lenna
12 months ago
I practiced a similar question where using a VPC for builds was suggested, but I wonder if that's overkill for just optimizing deployment.
KR
Kristin
1 year ago
I think storing artifacts in a Cloud Storage bucket could help with latency, but I'm not confident if it really speeds up deployment times.
BR
Breana
1 year ago
I'm not entirely sure, but removing the push step sounds risky. We need the image in Artifact Registry, right?
LI
Lindsey
1 year ago
I remember we discussed the importance of caching in Docker builds, so option B might be the right choice.
MI
Michal
1 year ago
Ah, the cache-from argument could be really helpful here. That might allow us to reuse cached layers from previous builds and cut down on build time. I'll take a closer look at option B.
MA
Martina
1 year ago
Okay, I think I've got a strategy here. Removing the Artifact Registry push step seems like the most straightforward way to speed things up, since we're already deploying to Cloud Run. I'll go with option A.
IS
Isabelle
1 year ago
Hmm, I'm a bit confused by the question. I'm not sure which step is causing the unnecessary delay. I'll need to do some research on Cloud Build and Cloud Run to figure this out.
LO
Lore
1 year ago
This looks like a tricky one. I'll need to carefully review the Cloud Build pipeline and think through the different options to optimize deployment times.
AU
Augustine
2 years ago
Haha, I bet the person who came up with option D was just trying to make the question more complex. Let's keep it simple and go with option B!
RE
Renay
2 years ago
User 4: Option B it is then, let's keep it simple.
FL
Floyd
2 years ago
User 3: Removing unnecessary steps is always a good idea.
SH
Sharika
2 years ago
User 2: Sounds good, that will help optimize deployment times.
FA
Fabiola
2 years ago
User 1: I agree, let's go with option B.
LA
Latrice
2 years ago
Option C is an interesting idea, but I'm not sure if storing the image artifacts in a Cloud Storage bucket will make a significant difference in deployment times.
LO
Louis
2 years ago
I agree with Daron. Storing image artifacts in a Cloud Storage bucket in the same region as the Cloud Run instance could also help optimize deployment times.
LA
Lai
2 years ago
I'm not a fan of option D. Creating a new Docker registry and VPC just for this build pipeline seems like overkill to me.
HY
Hyman
2 years ago
C) Store image artifacts in a Cloud Storage bucket in the same region as the Cloud Run instance.
AL
Alex
2 years ago
B) Add the --cache-from argument to the Docker build step in your build config file.
GE
Georgiann
2 years ago
A) Remove the step that pushes the container to Artifact Registry.
DA
Daron
2 years ago
I disagree. I believe adding the ---cache-from argument to the Docker build step would be more efficient.
CA
Cassie
2 years ago
Option B sounds like a good way to optimize deployment times. Caching the Docker build steps can definitely speed things up.
JE
Jeannine
2 years ago
User 4: Storing image artifacts in a Cloud Storage bucket can also help with optimization.
JU
Judy
2 years ago
User 3: Removing unnecessary steps can really make a difference in the pipeline.
PA
Pamella
2 years ago
User 2: I agree. It's important to optimize deployment times.
MA
Marilynn
2 years ago
User 1: Option B sounds like a good idea. Caching can definitely speed things up.
WI
Winifred
2 years ago
I think we should remove the step that pushes the container to Artifact Registry.