Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
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 48 discussion

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

Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Company Overview -
HipLocal is a community application designed to facilitate communication between people in close proximity. It is used for event planning and organizing sporting events, and for businesses to connect with their local communities. HipLocal launched recently in a few neighborhoods in Dallas and is rapidly growing into a global phenomenon. Its unique style of hyper-local community communication and business outreach is in demand around the world.

Executive Statement -
We are the number one local community app; it's time to take our local community services global. Our venture capital investors want to see rapid growth and the same great experience for new local and virtual communities that come online, whether their members are 10 or 10000 miles away from each other.

Solution Concept -
HipLocal wants to expand their existing service, with updated functionality, in new regions to better serve their global customers. They want to hire and train a new team to support these regions in their time zones. They will need to ensure that the application scales smoothly and provides clear uptime data.

Existing Technical Environment -
HipLocal's environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform. The HipLocal team understands their application well, but has limited experience in global scale applications. Their existing technical environment is as follows:
* Existing APIs run on Compute Engine virtual machine instances hosted in GCP.
* State is stored in a single instance MySQL database in GCP.
* Data is exported to an on-premises Teradata/Vertica data warehouse.
* Data analytics is performed in an on-premises Hadoop environment.
* The application has no logging.
* There are basic indicators of uptime; alerts are frequently fired when the APIs are unresponsive.

Business Requirements -
HipLocal's investors want to expand their footprint and support the increase in demand they are seeing. Their requirements are:
* Expand availability of the application to new regions.
* Increase the number of concurrent users that can be supported.
* Ensure a consistent experience for users when they travel to different regions.
* Obtain user activity metrics to better understand how to monetize their product.
* Ensure compliance with regulations in the new regions (for example, GDPR).
* Reduce infrastructure management time and cost.
* Adopt the Google-recommended practices for cloud computing.

Technical Requirements -
* The application and backend must provide usage metrics and monitoring.
* APIs require strong authentication and authorization.
* Logging must be increased, and data should be stored in a cloud analytics platform.
* Move to serverless architecture to facilitate elastic scaling.
* Provide authorized access to internal apps in a secure manner.
In order to meet their business requirements, how should HipLocal store their application state?

  • A. Use local SSDs to store state.
  • B. Put a memcache layer in front of MySQL.
  • C. Move the state storage to Cloud Spanner.
  • D. Replace the MySQL instance with Cloud SQL.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

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
fraloca
Highly Voted 3 years, 11 months ago
For me the answer is C. A is not valid because local SSD is volatile memory. B and D is bad solution because it don't reduce latency in world wide but they are a regional location.
upvoted 13 times
mastodilu
3 years, 6 months ago
exactly, plus the state is already stored in a single instance MySQL database in GCP, so it basically says "do nothing". Spanner is correct here
upvoted 3 times
gcp0omkar
3 years ago
"State is stored in a single instance MySQL database in GCP." so Cloud SQL is enough! (Option D) so Correct answer is D Spanner would be costly (Option C)
upvoted 1 times
...
...
...
thewalker
Most Recent 4 months, 1 week ago
Selected Answer: C
Cloud Spanner's Strengths: Cloud Spanner is a globally distributed, relational database service that offers high availability, scalability, and strong consistency. These features are crucial for HipLocal's global expansion and the need to ensure a consistent experience for users across regions. Scalability and Availability: Cloud Spanner can handle large amounts of data and automatically scales to meet demand. This addresses the business requirement of increasing the number of concurrent users and ensuring a consistent experience for users when they travel to different regions.
upvoted 1 times
thewalker
4 months, 1 week ago
Strong Consistency: Cloud Spanner provides strong consistency, meaning that all users see the same, up-to-date data, regardless of their location. This is essential for a community-based application like HipLocal, where users need to interact with the same information. Global Distribution: Cloud Spanner is globally distributed, allowing HipLocal to deploy their application in multiple regions and ensure low latency for users worldwide.
upvoted 1 times
thewalker
4 months, 1 week ago
Let's look at why the other options are less suitable: A. Use local SSDs to store state: Local SSDs are ephemeral storage and would be lost if a virtual machine instance is restarted. This is not a reliable solution for storing application state. B. Put a memcache layer in front of MySQL: Memcache can improve performance, but it doesn't address the scalability, availability, and consistency challenges of a single MySQL instance. D. Replace the MySQL instance with Cloud SQL: Cloud SQL is a managed MySQL service, but it doesn't offer the same level of global distribution, scalability, and consistency as Cloud Spanner.
upvoted 1 times
...
...
...
d_ella2001
4 months, 2 weeks ago
Selected Answer: C
correct answer is C
upvoted 1 times
...
santoshchauhan
8 months, 3 weeks ago
Selected Answer: C
C. Move the state storage to Cloud Spanner: Cloud Spanner is a fully managed, horizontally scalable database service with global distribution and strong consistency. It's well-suited for applications that require a high degree of scalability and reliability, making it a good choice for HipLocal as they expand globally. Given HipLocal's need for scalability and global distribution, Cloud Spanner (option C) is likely the best fit. It provides the scalability and global reach necessary for their expansion, along with the relational database capabilities that their application likely relies on. Cloud SQL (option D) is also a good choice if their current scale and distribution requirements can be met within its limits.
upvoted 1 times
...
wanrltw
1 year ago
Selected Answer: C
Moving the state storage to Cloud Spanner, is the best solution for HipLocal because Cloud Spanner is a globally distributed, horizontally scalable, and strongly consistent relational database service. Cloud Spanner provides high availability and can handle automatic scaling, backups, and updates. In addition, it provides support for distributed transactions, and it's designed to provide low latency and high throughput. Cloud Spanner can also help HipLocal meet their compliance requirements, as it supports HIPAA, GDPR, and other regulatory standards.
upvoted 2 times
...
__rajan__
1 year, 2 months ago
Selected Answer: C
Given HipLocal’s requirements for global expansion and high availability, moving the state storage to Cloud Spanner (option C) would likely be the most suitable choice.
upvoted 1 times
...
closer89
1 year, 6 months ago
Selected Answer: D
to meet their business requirements spanner is very expensive, we need to reduce costs after all cloud sql with multi-regional replication fits our needs https://cloud.google.com/sql/docs/mysql/replication#replication_use_cases
upvoted 2 times
...
brunoguzzo18
2 years, 3 months ago
Selected Answer: C
https://stackoverflow.com/questions/60412688/whats-the-difference-between-google-cloud-spanner-and-cloud-sql#:~:text=The%20main%20difference%20between%20Cloud,of%20writes%20per%20second%2C%20globally. C is correct for me.
upvoted 2 times
brunoguzzo18
2 years, 3 months ago
But, Spanner is not a formal relational DB so Cloud SQL is the best solution, plus is has the data replication for global purpose.
upvoted 1 times
...
...
tomato123
2 years, 3 months ago
Selected Answer: D
D is correct
upvoted 1 times
...
nhadi82
2 years, 4 months ago
Selected Answer: D
vote for D as also cloud SQL could be built for multi-region replica https://cloud.google.com/blog/products/databases/introducing-cross-region-replica-for-cloud-sql
upvoted 2 times
closer89
1 year, 6 months ago
replica is OK to read data. but you have to write to master node which could be in a different continent https://cloud.google.com/sql/docs/mysql/replication#read-replicas https://cloud.google.com/sql/docs/mysql/replication#cross-region-read-replicas
upvoted 1 times
...
...
akshaychavan7
2 years, 4 months ago
Selected Answer: C
Let's go with Cloud Spanner as it is the only supported global solution.
upvoted 1 times
...
brewpike
2 years, 6 months ago
C- Spanner, business requirements are to expand globally.
upvoted 1 times
...
dishum
2 years, 8 months ago
Looks like C is the answer
upvoted 2 times
...
GCPCloudArchitectUser
2 years, 9 months ago
Selected Answer: D
CloudSql is better and cheaper option compared to Spanner
upvoted 2 times
hitmax87
2 years, 7 months ago
CloudSql is regional.
upvoted 1 times
...
...
syu31svc
3 years, 4 months ago
"Expand availability of the application to new regions" "Ensure a consistent experience for users when they travel to different regions" The above would indicate use of Cloud Spanner; answer should be C
upvoted 3 times
syu31svc
3 years, 3 months ago
Changing to D Cloud SQL since qn50 answer is Cloud SQL Matter of consistency I believe
upvoted 1 times
Kadhem
11 months, 1 week ago
each question for case study is independent
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 ...