exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam

Exam Professional Cloud Developer topic 1 question 95 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 95
Topic #: 1
[All Professional Cloud Developer Questions]

You are developing a marquee stateless web application that will run on Google Cloud. The rate of the incoming user traffic is expected to be unpredictable, with no traffic on some days and large spikes on other days. You need the application to automatically scale up and down, and you need to minimize the cost associated with running the application. What should you do?

  • A. Build the application in Python with Firestore as the database. Deploy the application to Cloud Run.
  • B. Build the application in C# with Firestore as the database. Deploy the application to App Engine flexible environment.
  • C. Build the application in Python with CloudSQL as the database. Deploy the application to App Engine standard environment.
  • D. Build the application in Python with Firestore as the database. Deploy the application to a Compute Engine managed instance group with autoscaling.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
p4
Highly Voted 2 years, 9 months ago
Why C? I chose option A because of the DB option. both Cloud run (A) and App Engine Standard (C) can scale to zero, so we need to find out the correct DB Firestore vs CloudSQL since we don’t know any details if data structures require relational or noSQL, I’d go for Firestore because it is more flexible in scalability than CloudSQL, and also you only pay per storage usage + operations
upvoted 11 times
closer89
1 year, 6 months ago
"you need to minimize the cost associated with running the application" cloud run is cheaper, with 0.10 time granularity
upvoted 1 times
...
...
GCPCloudArchitectUser
Highly Voted 2 years, 8 months ago
Selected Answer: A
I agree with A as it is the only one fits for scale up and down =
upvoted 6 times
...
dneves
Most Recent 4 months, 1 week ago
Selected Answer: A
Answer A. Python + Firestore + Cloud Run: Truly serverless (scales to zero) Pay only for actual usage Handles spikes well Firestore scales automatically Minimal management overhead Lowest cost when no traffic
upvoted 1 times
...
alpha_canary
6 months, 2 weeks ago
Selected Answer: A
A: Building the application in Python with Firestore as the database and deploying the application to Cloud Run is a good approach. Cloud Run is designed to scale up and down automatically, even down to zero, which can help minimize costs when there's no traffic. Firestore is a serverless, NoSQL document database that can scale automatically to meet your application's needs. Why C is rejected? C: While App Engine standard environment can scale down to zero instances, CloudSQL is not serverless and you are billed for the time that the database instance is running, which could increase costs when compared to Firestore.
upvoted 1 times
...
Aeglas
11 months, 1 week ago
Selected Answer: A
Also Firestore has a free tier quota
upvoted 1 times
...
braska
11 months, 2 weeks ago
Selected Answer: A
Option A is a suitable choice for building a stateless web application with unpredictable traffic, aiming to automatically scale up and down while minimizing costs
upvoted 1 times
...
__rajan__
1 year, 1 month ago
Selected Answer: A
A is best suited here.
upvoted 1 times
...
[Removed]
1 year, 8 months ago
Selected Answer: A
Both Cloud Run and App Engine Standard Environment allow scaling to zero (which minimize the cost), but Cloud SQL can't be minimized to zero while firestore is measured based on CPU usage. So from the cost point of view, A is the answer
upvoted 1 times
...
omermahgoub
1 year, 9 months ago
Answer is A: To minimize the cost of running the application and to allow it to automatically scale up and down based on incoming traffic, you should build the application in Python with Firestore as the database, and deploy it to Cloud Run. B and C, which involve deploying the application to App Engine, may also allow the application to automatically scale, but they may not be as cost-effective as Cloud Run. Option D, which involves deploying the application to a Compute Engine managed instance group, would allow the application to automatically scale, but it would not be as cost-effective as Cloud Run, as you would have to pay for the resources that you use even when there is no traffic.
upvoted 2 times
...
zellck
1 year, 10 months ago
Selected Answer: A
A is the answer.
upvoted 1 times
...
tomato123
2 years, 2 months ago
Selected Answer: A
A is correct
upvoted 2 times
...
kinoko1330
2 years, 2 months ago
Selected Answer: A
A because of "stateless web app"
upvoted 1 times
...
htakami
2 years, 7 months ago
It's simple, we need a stateless web app (not relational DB as Cloud SQL), and sometimes it scales down to zero utilization (only GAE flex & Cloud Run can do this). I'll go with option A as well.
upvoted 1 times
Kadhem
11 months, 2 weeks ago
GAE flex don't scale to zero
upvoted 1 times
...
htakami
2 years, 7 months ago
And if you were wondering why not B, C# is not a supported language for GAE
upvoted 1 times
...
...
ESP_SAP
2 years, 7 months ago
Correct Answer is A; They are talking about minimize cost, with Cloud SQL isn't cheaper than Firestore.
upvoted 1 times
...
Blueocean
2 years, 9 months ago
Agree with Option C
upvoted 2 times
...
scaenruy
2 years, 9 months ago
I vote C
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago