Exam Professional Cloud Developer All QuestionsBrowse all questions from this exam
Go to Exam
Question 83

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 for HipLocal to store application state and meet their stated business requirements, which database service should they migrate to?

    Correct Answer: A

    Cloud Spanner is the best choice for HipLocal's database service because it is designed to support global scalability and strong consistency, which are key requirements for HipLocal as they expand to new regions and seek to provide a consistent experience for users worldwide. Cloud Spanner can handle a high number of concurrent users and ensures data consistency across multiple regions, which aligns with HipLocal's business and technical needs. Additionally, as a fully managed service, it reduces infrastructure management time and costs, adhering to Google-recommended practices for cloud computing.

Discussion
celia20200410Option: A

https://cloud.google.com/blog/products/databases/spanner-relational-database-for-all-size-applications-faqs https://cloud.google.com/architecture/best-practices-cloud-spanner-gaming-database#select_a_data_locality_to_meet_compliance_requirements https://cloud.google.com/blog/products/gcp/introducing-cloud-spanner-a-global-database-service-for-mission-critical-applications A. Cloud Spanner - global service - supports durably store application data - supports GDPR, to meet data locality

GoatSack

Agree with Celia.

mastodiluOption: D

I guess that the answer is D because of the GDPR

ralf_cc

Tend to agree with you

GCPCloudArchitectUser

Seriously you want to spin up cloud sql in every region? …

alex8081

" Reduce infrastructure management time and cost".. Cloud Spanner is a database for business critical applications that completely replaces one or more Data Warehouses... is out of scope. I Vote Cloud SQL

closer89

what about management time for cloud sql clusters? you can tune your cloud spanner instances, nobody forces you to use 1000 nodes. 1. Cloud Spanner charges for the amount of storage used per month. The pricing starts at $0.30/GB/month for regional storage and $0.60/GB/month for multi-regional storage. 2. Cloud Spanner charges for the number of nodes used per month. The pricing starts at $0.90/hour/node for regional instances and $1.44/hour/node for multi-regional instances. 3. Cloud Spanner charges for the amount of data processed per month. The pricing starts at $0.06/GB for regional instances and $0.12/GB for multi-regional instances

closer89

isnt it affordable for hiplocal company that wants to "left footprint"??

TNT87

So spanner doesnt support GDPR??? kkkkkkkkkkkkkk

thewalkerOption: A

The best answer here is A. Cloud Spanner . Here's why: Global Scalability and Consistency: HipLocal needs to expand globally and ensure a consistent experience for users across regions. Cloud Spanner is a globally distributed, strongly consistent database that can handle high volumes of data and transactions across multiple regions. This ensures that users have a seamless experience regardless of their location. Strong Consistency: HipLocal's application state needs to be consistent, especially for critical operations like user authentication, event scheduling, and payment processing. Cloud Spanner's strong consistency guarantees that all data is updated across all replicas simultaneously, preventing data inconsistencies and ensuring data integrity. Scalability: HipLocal needs to increase the number of concurrent users they can support. Cloud Spanner is designed for scalability, allowing HipLocal to easily add capacity as their user base grows.

thewalker

Reduced Management Overhead: Cloud Spanner is a fully managed service, meaning HipLocal doesn't need to worry about managing infrastructure, backups, or security patches. This reduces their management overhead and allows them to focus on developing their application.

thewalker

Why other options are less suitable: B. Cloud Datastore: While Cloud Datastore is a good choice for NoSQL data, it's eventually consistent, meaning data might not be immediately updated across all replicas. This could lead to inconsistencies in application state, which is not ideal for HipLocal's requirements. C. Cloud Memorystore as a cache: Cloud Memorystore is a great caching solution, but it's not a primary database. It's used to improve performance by storing frequently accessed data in memory. It's not suitable for storing application state or handling transactions. D. Separate Cloud SQL clusters for each region: This approach would require managing multiple databases, which can be complex and expensive. It also wouldn't provide the same level of global consistency and scalability as Cloud Spanner.

santoshchauhanOption: A

Here's how Cloud Spanner aligns with HipLocal's business requirements: It allows for a global distribution of databases, ensuring users have a consistent experience no matter their location. Cloud Spanner's horizontal scalability supports an increasing number of concurrent users, which is necessary for HipLocal's rapid growth. It offers high availability and regional data replication, which can help HipLocal ensure compliance with various regional data regulations like GDPR. Managed service reduces the infrastructure management time and cost, meeting another of HipLocal's key requirements.

RajanOption: A

A is best suited.

TQM__9MDOption: A

I think A

mrvergaraOption: D

Cloud Spanner is a highly scalable, globally-distributed database service offered by Google Cloud, but it may not be the best fit for HipLocal's needs. While Cloud Spanner provides automatic and instant scaling, strong consistency guarantees, and high availability, it also comes with a higher operational overhead and cost compared to other Google Cloud databases. Additionally, Cloud Spanner is designed for large, mission-critical applications that require strict consistency guarantees across multiple regions, which may not be necessary for HipLocal's current requirements. In this case, it would be more appropriate for HipLocal to separate Cloud SQL clusters for each region to store their application state, as this solution would provide the necessary data storage capabilities and be more cost-effective for their current requirements.

mrvergara

Changing to A because of this requirement: Ensure a consistent experience for users when they travel to different regions.

tomato123Option: A

A is correct

syu31svcOption: A

This is similar to qn 48; I would say A is the answer

syu31svc

Changing to D as qn 50 answer is Cloud SQL; consistency sake

GoatSack

From case study instructions: "Each question is independent of the other questions in this case study." I am leaning towards Spanner here. What do you think?