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 6 Question 103 Discussion

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

You work on an application that relies on Cloud Spanner as its main datastore. New application features have occasionally caused performance regressions. You want to prevent performance issues by running an automated performance test with Cloud Build for each commit made. If multiple commits are made at the same time, the tests might run concurrently. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Lovetta
26 days ago
I bet the developers who come up with these exam questions have a blast trying to trip us up. 'Delete the project after the test?' Sounds like a recipe for disaster!
upvoted 0 times
...
Ivan
1 months ago
Why not just use a single project and instance, and reset the data state after each test? Option C sounds like the most efficient and cost-effective approach.
upvoted 0 times
...
Earleen
1 months ago
Creating a new project for every build is a bit overkill, in my opinion. Option A might work, but it could get expensive with all the project creation and deletion.
upvoted 0 times
Jonelle
13 days ago
C) Create a project with a Cloud Spanner instance and the required data. Adjust the Cloud Build build file to automatically restore the data to its previous state after the test is run.
upvoted 0 times
...
Ty
19 days ago
B) Create a new Cloud Spanner instance for every build. Load the required data. Delete the Cloud Spanner instance after the test is run.
upvoted 0 times
...
Mabel
27 days ago
A) Create a new project with a random name for every build. Load the required data. Delete the project after the test is run.
upvoted 0 times
...
...
Mel
2 months ago
I'm not sure, I think option D could also work well. What do you think?
upvoted 0 times
...
Janine
2 months ago
I like the idea of using the Cloud Spanner emulator locally, as it avoids the overhead of provisioning and deleting instances. Option D could be a good choice if the emulator accurately represents the production environment.
upvoted 0 times
Glennis
21 days ago
I agree, using the emulator locally seems like a more efficient approach.
upvoted 0 times
...
Brittani
1 months ago
Option D sounds like a good idea. It would definitely save time and resources.
upvoted 0 times
...
...
Emmett
2 months ago
Option C seems the most practical. Restoring the data state after each test run is key to ensuring reliable and consistent performance results.
upvoted 0 times
Tandra
2 days ago
Yeah, using the Cloud Spanner emulator locally could also work, but it's not as efficient as option C.
upvoted 0 times
...
Florinda
5 days ago
Creating a new project or instance for every build seems like a lot of unnecessary work.
upvoted 0 times
...
Crista
8 days ago
I agree, maintaining the data state is crucial for accurate performance testing.
upvoted 0 times
...
Enola
25 days ago
Option C seems like the best choice. It ensures the data is restored after each test run.
upvoted 0 times
...
...
Lore
2 months ago
I agree with Talia. Option C seems like the most efficient solution.
upvoted 0 times
...
Talia
2 months ago
I think option C is the best choice.
upvoted 0 times
...
Lili
2 months ago
I think option A is the safest choice to avoid integration issues.
upvoted 0 times
...
Melvin
2 months ago
Option B? Really? That's just asking for trouble. I'd go with Option C to keep everyone on the same page.
upvoted 0 times
Marya
1 months ago
I'd go with Option C to keep everyone on the same page.
upvoted 0 times
...
Asha
1 months ago
Option B? Really? That's just asking for trouble.
upvoted 0 times
...
...
Carmen
2 months ago
I prefer option C, it allows for daily integration into the main branch.
upvoted 0 times
...

Save Cancel