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

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?
D) Start the Cloud Spanner emulator locally. Load the required data. Shut down the emulator after the test is run.
A) Create a new project with a random name for every build. Load the required data. Delete the project after the test is run.
B) Create a new Cloud Spanner instance for every build. Load the required data. Delete the Cloud Spanner instance after the test is run.
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.

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

by Nickolas at Mar 09, 2025, 12:51 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
Casie
9 months ago
C is definitely the most practical approach here.
upvoted 0 times
...
Brigette
9 months ago
Surprised that D is even an option, does the emulator really work well?
upvoted 0 times
...
Larue
10 months ago
A sounds like a hassle, too many projects to manage!
upvoted 0 times
...
Dean
10 months ago
I disagree, C would be more efficient in the long run.
upvoted 0 times
...
Robt
10 months ago
Option B seems like the best choice for isolation.
upvoted 0 times
...
Tamesha
10 months ago
Starting the emulator seems like a safe bet, but I’m not entirely confident if it would mimic the production environment accurately enough.
upvoted 0 times
...
Luisa
11 months ago
I practiced a similar question where we had to manage resources efficiently. I feel like option B could be overkill, creating too many instances.
upvoted 0 times
...
Chandra
11 months ago
I think option C sounds familiar; it might help maintain a consistent state, but I wonder if it could lead to data conflicts with concurrent builds.
upvoted 0 times
...
Joseph
11 months ago
I remember we discussed the pros and cons of creating new instances for tests, but I'm not sure if that's the best approach here.
upvoted 0 times
...
Annmarie
11 months ago
I'm leaning towards option B. Creating a new Cloud Spanner instance for each build could help isolate the tests and prevent any interference.
upvoted 0 times
...
Devorah
11 months ago
I think option C might be the way to go. Restoring the data state after the test seems like the most reliable approach.
upvoted 0 times
...
Sabra
11 months ago
Ah, I see. Using the Cloud Spanner emulator could be a good solution, but I'll need to make sure the data is properly loaded and unloaded.
upvoted 0 times
...
Viola
11 months ago
Hmm, creating a new project for every build sounds like a lot of overhead. I wonder if there's a more efficient way to handle this.
upvoted 0 times
...
Laura
11 months ago
This seems like a tricky one. I'll need to think through the options carefully to make sure I don't miss anything.
upvoted 0 times
...
Lovetta
1 year 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 year 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
Franchesca
1 year ago
That makes sense, it's important to optimize the testing process to prevent performance regressions.
upvoted 0 times
...
Lai
1 year ago
I agree, it would save time and resources compared to creating new projects or instances for every build.
upvoted 0 times
...
Amie
1 year ago
Option C sounds like the most efficient and cost-effective approach.
upvoted 0 times
...
...
Earleen
1 year 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
Simona
1 year 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
...
Jonelle
1 year 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
1 year 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
1 year 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
1 year ago
I'm not sure, I think option D could also work well. What do you think?
upvoted 0 times
...
Janine
1 year 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
1 year ago
I agree, using the emulator locally seems like a more efficient approach.
upvoted 0 times
...
Brittani
1 year ago
Option D sounds like a good idea. It would definitely save time and resources.
upvoted 0 times
...
...
Emmett
1 year 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
1 year ago
Yeah, using the Cloud Spanner emulator locally could also work, but it's not as efficient as option C.
upvoted 0 times
...
Florinda
1 year ago
Creating a new project or instance for every build seems like a lot of unnecessary work.
upvoted 0 times
...
Crista
1 year ago
I agree, maintaining the data state is crucial for accurate performance testing.
upvoted 0 times
...
Enola
1 year ago
Option C seems like the best choice. It ensures the data is restored after each test run.
upvoted 0 times
...
...
Lore
1 year ago
I agree with Talia. Option C seems like the most efficient solution.
upvoted 0 times
...
Talia
1 year ago
I think option C is the best choice.
upvoted 0 times
...
Lili
1 year ago
I think option A is the safest choice to avoid integration issues.
upvoted 0 times
...
Melvin
1 year 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 year ago
I'd go with Option C to keep everyone on the same page.
upvoted 0 times
...
Asha
1 year ago
Option B? Really? That's just asking for trouble.
upvoted 0 times
...
...
Carmen
1 year ago
I prefer option C, it allows for daily integration into the main branch.
upvoted 0 times
...

Save Cancel