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

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.

Which database should HipLocal use for storing user activity?

    Correct Answer: A

    To meet HipLocal's needs for storing user activity data, BigQuery is the most suitable option. BigQuery is designed for handling large volumes of data and provides powerful analytics capabilities, which align with the requirement to obtain user activity metrics for better understanding and monetization. It is cost-effective due to its pay-per-use model and complies with regulations, aiding infrastructure management through its scalable and managed service attributes. These features make it an ideal choice over other options for storing and analyzing user activity data.

Discussion
fosky94Option: A

In the case study is stated: "Obtain user activity metrics to better understand how to monetize their product", which means that they'll need to analyse the user activity, so... I'll go with answer A (BigQuery)

syu31svc

Agree with you on this one

boofOption: D

#37 "Your existing application keeps user state information in a single MySQL database. This state information is very user-specific and depends heavily on how long a user has been using an application. The MySQL database is causing challenges to maintain and enhance the schema for various users. Which storage option should you choose?" https://cloud.google.com/datastore/docs/concepts/overview#what_its_good_for "Datastore/Firestore can store and query the following types of data: User profiles that deliver a customized experience based on the user’s past activities and preferences" I feel like this is a toss up between these two since we're talking about user profiles/data, would vote for D here bc MySQL offers a really rigid schema and isn't well suited to massive scaling either.

nehaxlpbOption: A

Bigquery for user activity analysis . And also the user activity is kind of raw data which being used to segment user or according age , choice etc so Bigquery fits best fr this use cases

NidieOption: D

I choose D, datastore.

thewalkerOption: A

The best answer here is A. BigQuery . Here's why: Scalability and Analytics: HipLocal needs to store and analyze user activity data to understand how to monetize their product. BigQuery is designed for petabyte-scale data storage and offers powerful analytics capabilities. It's ideal for handling the large volumes of user activity data that HipLocal will generate as they expand globally. Cost-Effectiveness: BigQuery is pay-per-use, making it cost-effective for storing large amounts of data that might not be accessed frequently. This aligns with HipLocal's goal of reducing infrastructure management costs. Compliance: BigQuery is a compliant platform, meeting requirements like GDPR. This is crucial for HipLocal as they expand into new regions with varying data privacy regulations.

thewalker

Why other options are less suitable: B. Cloud SQL: While Cloud SQL is a good choice for relational databases, it's not designed for the massive scale and analytics needs of user activity data. It can be expensive for large datasets. C. Cloud Spanner: Cloud Spanner is a globally distributed, strongly consistent database. While it's excellent for transactional data, it's overkill for user activity data that doesn't require strong consistency. It's also more complex and expensive than BigQuery. D. Cloud Datastore: Cloud Datastore is a NoSQL database that's good for real-time updates. However, its query capabilities are less powerful than BigQuery, and it's not as well-suited for large-scale analytics.

santoshchauhanOption: C

Here's why Cloud Spanner is the best fit for HipLocal's needs: Global Scalability: Cloud Spanner can scale horizontally to handle increased loads and number of concurrent users, which is aligned with the rapid growth that HipLocal is experiencing. Strong Consistency: It provides strong consistency guarantees, ensuring that users have a consistent experience regardless of the region they're accessing the application from. High Availability: Spanner's built-in replication across multiple regions makes it highly available, which helps to meet uptime requirements and ensure compliance with regulations like GDPR that may require data to be stored in certain regions. Managed Service: As a fully managed service, it reduces the time and cost associated with infrastructure management, which meets the business requirement to minimize management overhead.

RajanOption: D

For Storing user data Datastore is best.

Rajan

I think A would be better fit for this. Please ignore the above answer.

sbonessiOption: A

A (BigQuery) is more apropiated for user activities. If it was manage user states, I would consider D (Datastore/Firestore) but this is not the case. So, from my point of view, A is the correct answer.

tomato123Option: A

A is correct

brewpikeOption: A

Toss b/w A and D . It depends what needs to be done on user activity, if analytics then A. (Big query) else if customizing customer experience then D (Datastore)

GCPCloudArchitectUserOption: D

I agree with having to use Datstore

mariorossiOption: A

A. database only for user activity