New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Associate Cloud Engineer Exam - Topic 4 Question 99 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 99
Topic #: 4
[All Associate Cloud Engineer Questions]

Your company is running a three-tier web application on virtual machines that use a MySQL database. You need to create an estimated total cost of cloud infrastructure to run this application on Google Cloud instances and Cloud SQL. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Marica
3 months ago
I disagree, A is way easier than B's load testing approach.
upvoted 0 times
...
Alexia
3 months ago
Wait, D? A spreadsheet for this? Seems old school!
upvoted 0 times
...
Matthew
3 months ago
C sounds complicated, not sure if it's necessary.
upvoted 0 times
...
Franklyn
4 months ago
I think B could give more accurate results with real load testing.
upvoted 0 times
...
Belen
4 months ago
A is the best option, super straightforward!
upvoted 0 times
...
Stefan
4 months ago
Creating a spreadsheet with formulas seems like a lot of work, but it could help visualize different scenarios. I wonder if it's more efficient than just using the calculator directly.
upvoted 0 times
...
Nida
4 months ago
I feel like I saw something about using templates in the Pricing Calculator, but I can't recall if the Cloud Operations template is the right one for a web app.
upvoted 0 times
...
Audry
4 months ago
I think option B sounds familiar; running a load test could give real insights, but it might take more time than just using the calculator.
upvoted 0 times
...
Margurite
5 months ago
I remember practicing with the Google Cloud Pricing Calculator, but I'm not sure if I should compare it to on-premises machines or just focus on the cloud resources.
upvoted 0 times
...
Earleen
5 months ago
I'm a bit confused on the best approach. Should we be creating our own spreadsheet to track the costs, or is the Pricing Calculator the way to go? I'm not sure which method would be more accurate or efficient.
upvoted 0 times
...
Hermila
5 months ago
I think the key here is to be as detailed as possible in our cost estimation. Using the Cloud Operations template in the Pricing Calculator seems like a good way to capture all the relevant components of our web application.
upvoted 0 times
...
Loreta
5 months ago
Hmm, I'm a bit unsure about this one. Should we also consider running a smaller-scale test on Google Cloud to get a more accurate idea of the actual costs? That might give us a better sense of the real-world usage and pricing.
upvoted 0 times
...
Eladia
5 months ago
This looks like a straightforward cost estimation question. I'd start by using the Google Cloud Pricing Calculator to get a detailed breakdown of the costs for the different cloud resources we'd need.
upvoted 0 times
...
Derrick
1 year ago
Hah, creating a spreadsheet with different combinations? That's a bit overkill, don't you think? Option A is where it's at.
upvoted 0 times
...
Germaine
1 year ago
I think option D could also work. Creating a spreadsheet with different resource combinations can help us analyze the costs effectively.
upvoted 0 times
...
Celestina
1 year ago
Option C is interesting, but I'm not sure if the Cloud Operations template will give me enough flexibility to model our specific use case.
upvoted 0 times
Owen
1 year ago
C) Option C is a good starting point, but you can always customize the template to better fit our specific use case.
upvoted 0 times
...
Gracie
1 year ago
B) Implement a similar architecture on Google Cloud, and run a reasonable load test on a smaller scale. Check the billing information, and calculate the estimated costs based on the real load your system usually handles.
upvoted 0 times
...
Helaine
1 year ago
A) Use the Google Cloud Pricing Calculator to determine the cost of every Google Cloud resource you expect to use. Use similar size instances for the web server, and use your current on-premises machines as a comparison for Cloud SQL.
upvoted 0 times
...
...
Loise
1 year ago
I prefer option B. Running a load test on a smaller scale will provide more accurate cost estimates.
upvoted 0 times
...
Laura
1 year ago
I agree with Phyliss. Using our current on-premises machines as a comparison will give us a good estimate.
upvoted 0 times
...
Emilio
1 year ago
I agree with Corrina. Using the pricing calculator to account for every resource is the best approach here.
upvoted 0 times
...
Corrina
1 year ago
Option A seems like the way to go. The Google Cloud Pricing Calculator is a reliable tool to get a detailed cost estimate.
upvoted 0 times
Micheal
1 year ago
B) I agree, it's important to have an accurate estimate before making the switch to Google Cloud.
upvoted 0 times
...
Tonja
1 year ago
A) Use the Google Cloud Pricing Calculator to determine the cost of every Google Cloud resource you expect to use. Use similar size instances for the web server, and use your current on-premises machines as a comparison for Cloud SQL.
upvoted 0 times
...
...
Phyliss
1 year ago
I think option A is the best approach. We need to compare the costs with our current setup.
upvoted 0 times
...

Save Cancel