MENU
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?
Suggested Answer: D
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
40 comments · newest first
CA
Casie
11 months ago
C is definitely the most practical approach here.
BR
Brigette
11 months ago
Surprised that D is even an option, does the emulator really work well?
LA
Larue
11 months ago
A sounds like a hassle, too many projects to manage!
DE
Dean
11 months ago
I disagree, C would be more efficient in the long run.
RO
Robt
12 months ago
Option B seems like the best choice for isolation.
TA
Tamesha
12 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.
LU
Luisa
1 year 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.
CH
Chandra
1 year 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.
JO
Joseph
1 year 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.
AN
Annmarie
1 year 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.
DE
Devorah
1 year ago
I think option C might be the way to go. Restoring the data state after the test seems like the most reliable approach.
SA
Sabra
1 year 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.
VI
Viola
1 year 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.
LA
Laura
1 year ago
This seems like a tricky one. I'll need to think through the options carefully to make sure I don't miss anything.
LO
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!
IV
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.
FR
Franchesca
1 year ago
That makes sense, it's important to optimize the testing process to prevent performance regressions.
LA
Lai
1 year ago
I agree, it would save time and resources compared to creating new projects or instances for every build.
AM
Amie
1 year ago
Option C sounds like the most efficient and cost-effective approach.
EA
Earleen
2 years 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.
SI
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.
JO
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.
TY
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.
MA
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.
ME
Mel
2 years ago
I'm not sure, I think option D could also work well. What do you think?
JA
Janine
2 years 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.
GL
Glennis
1 year ago
I agree, using the emulator locally seems like a more efficient approach.
BR
Brittani
1 year ago
Option D sounds like a good idea. It would definitely save time and resources.
EM
Emmett
2 years ago
Option C seems the most practical. Restoring the data state after each test run is key to ensuring reliable and consistent performance results.
TA
Tandra
1 year ago
Yeah, using the Cloud Spanner emulator locally could also work, but it's not as efficient as option C.
FL
Florinda
1 year ago
Creating a new project or instance for every build seems like a lot of unnecessary work.
CR
Crista
1 year ago
I agree, maintaining the data state is crucial for accurate performance testing.
EN
Enola
1 year ago
Option C seems like the best choice. It ensures the data is restored after each test run.
LO
Lore
2 years ago
I agree with Talia. Option C seems like the most efficient solution.
TA
Talia
2 years ago
I think option C is the best choice.
LI
Lili
2 years ago
I think option A is the safest choice to avoid integration issues.
ME
Melvin
2 years ago
Option B? Really? That's just asking for trouble. I'd go with Option C to keep everyone on the same page.
MA
Marya
2 years ago
I'd go with Option C to keep everyone on the same page.
AS
Asha
2 years ago
Option B? Really? That's just asking for trouble.
CA
Carmen
2 years ago
I prefer option C, it allows for daily integration into the main branch.