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.
HipLocal wants to reduce the number of on-call engineers and eliminate manual scaling.
Which two services should they choose? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.BC.
HipLocal wants to expand their community application to new regions to better serve their global customers. They have a mix of on-premises hardware and infrastructure running in Google Cloud Platform (GCP). They want to ensure that the application scales smoothly and provides clear uptime data. HipLocal also wants to reduce the number of on-call engineers and eliminate manual scaling. They want to adopt Google-recommended practices for cloud computing.
The technical requirements include providing usage metrics and monitoring, strong authentication and authorization for APIs, increased logging, and storing data in a cloud analytics platform. They also need to move to a serverless architecture to facilitate elastic scaling and provide authorized access to internal apps in a secure manner.
The two services that HipLocal should choose are: A. Use Google App Engine services. B. Use serverless Google Cloud Functions.
Google App Engine services provide a fully managed platform for building and deploying web applications and services. It supports multiple languages such as Java, Python, PHP, and Go. It allows developers to focus on writing code, and Google manages the underlying infrastructure. App Engine also provides automatic scaling based on application traffic, so HipLocal can easily handle increased user demand without worrying about manual scaling.
Serverless Google Cloud Functions allow developers to write and deploy code that responds to events, such as changes in data, without managing the underlying infrastructure. It supports multiple languages such as Node.js, Python, and Go. It can be used for a variety of use cases, including mobile backends, IoT event processing, and more. By using serverless functions, HipLocal can eliminate the need for manual scaling and reduce the number of on-call engineers.
Option C, using Knative to build and deploy serverless applications, is not necessary in this scenario. While Knative can help manage serverless applications and reduce operational overhead, it is a more advanced option and may not be necessary for HipLocal's needs.
Option D, using Google Kubernetes Engine for automated deployments, may be useful in certain scenarios but may not be necessary for HipLocal's needs. Kubernetes provides a platform for managing containerized workloads, but it may require more configuration and management than App Engine or Cloud Functions.
Option E, using a large Google Compute Engine cluster for deployments, may not be the best option for HipLocal. Compute Engine provides virtual machine instances for running applications, but it requires more management overhead than App Engine or Cloud Functions. It also may not provide the automatic scaling that HipLocal needs for handling increased user demand.
In summary, HipLocal should choose Google App Engine services and serverless Google Cloud Functions to meet their business and technical requirements, reduce infrastructure management time and cost, and adopt Google-recommended practices for cloud computing.