Professional Cloud Developer Exam QuestionsBrowse all questions from this exam

Professional Cloud Developer Exam - Question 47


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.)

Show Answer
Correct Answer: ABC

To meet HipLocal's requirements of reducing the number of on-call engineers and eliminating manual scaling, they should use services that offer serverless architecture and automatic scaling. Google App Engine is a fully managed serverless platform that automatically handles scaling, load balancing, and infrastructure management, supporting deployment to multiple regions, which ensures global availability. Similarly, Google Cloud Functions is a serverless, event-driven platform for executing code that automatically scales with demand, reducing the need for manual intervention. Both services align with the goals of scalability, reduced management burden, and global reach.

Discussion

17 comments
Sign in to comment
saurabh1805Options: AB
Nov 9, 2020

A and B are correct option here.

akshaychavan7Options: CD
Jul 5, 2022

App Engine cannot be a solution here as it limits the application to be in a single region. We need to note that the case study has explicitly mentioned that the application needs to be global, which means multi-regional. So, I will go with C & D.

syu31svcOptions: AB
Jul 3, 2021

https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed#apps_with_automatic_scaling A and B for sure; "eliminate manual scaling" as per what the qn states

dishumOptions: AB
Mar 28, 2022

AB is correct

brunoguzzo18Options: CD
Aug 30, 2022

App must be global

raja77Options: AB
Jan 19, 2022

https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed#apps_with_automatic_scaling

gfr892Options: DE
Jan 22, 2022

App Engine and Cloud Functions are regional. D and E are correct, because they are global and they have autoscaler for deployments.

gfr892
Jan 22, 2022

Correction: C and D are correct. https://cloud.google.com/knative https://cloud.google.com/blog/products/serverless/knative-based-cloud-run-services-are-ga https://cloud.google.com/run/docs/multiple-regions

hitmax87Options: CD
Apr 3, 2022

C+D are correct. Because k8s is global plus on-premises nodes can be connected.

nhadi82Options: CD
Jul 19, 2022

Vote for C & D

nehaxlpbOptions: CD
Jul 28, 2022

https://cloud.google.com/kubernetes-engine/docs/concepts/traffic-management

tomato123Options: CD
Aug 20, 2022

CD are correct

telpOptions: CD
Jan 12, 2023

C and D because need to be global

minagmaxwellOptions: AB
Jul 13, 2023

you CAN go global with app engine and cloud functions

RajanOptions: AB
Sep 19, 2023

I Think It should be A nd B for serverless autoscaling. Since there are extra steps involved in configuring Knative it is not fit for this situation.

santoshchauhanOptions: AB
Mar 7, 2024

A. Google App Engine: This is a fully managed serverless platform that automatically scales your application up and down while balancing the load. With App Engine, you don't need to manage the underlying infrastructure, and it scales automatically in response to the traffic it receives. This can significantly reduce the operational overhead and the need for on-call engineers to handle scaling issues. B. Google Cloud Functions: This is another serverless execution environment that automatically scales the number of instances running your function in response to the incoming event rate. This is ideal for applications that respond to events (e.g., HTTP requests, Cloud Pub/Sub events). Like App Engine, it abstracts away infrastructure management and auto-scales based on demand.

d_ella2001Options: AB
Jul 13, 2024

Google App Engine and Google Cloud Functions are the best choices to meet HipLocal's requirements for reducing on-call engineer responsibilities and eliminating manual scaling. App Engine is a fully managed serverless platform that supports deployment to multiple regions, ensuring that your application can serve users around the world with low latency. You can choose the regions where you want to deploy your application, and Google manages the underlying infrastructure to provide high availability and automatic scaling. Cloud Functions can be deployed in multiple regions, allowing you to run your functions close to your users and other services they interact with. This reduces latency and improves performance.

thewalkerOptions: BD
Jul 17, 2024

The two best services for HipLocal to choose are: B. Use serverless Google Cloud Functions. D. Use Google Kubernetes Engine for automated deployments. Here's why: Cloud Functions: Cloud Functions is a serverless platform that automatically scales based on demand. This eliminates the need for manual scaling and reduces the workload on on-call engineers. Kubernetes Engine: Kubernetes Engine (GKE) is a managed Kubernetes service that provides automated deployments, scaling, and self-healing capabilities. This reduces the need for manual intervention and frees up engineers to focus on other tasks.

thewalker
Jul 17, 2024

Let's look at why the other options are less ideal: A. Use Google App Engine services: App Engine is a good option for serverless applications, but it might not be as flexible as Cloud Functions for specific tasks like authentication or background processing. C. Use Knative to build and deploy serverless applications: Knative is a great option for building and deploying serverless applications, but it requires more configuration and management than Cloud Functions. E. Use a large Google Compute Engine cluster for deployments: While Compute Engine provides flexibility, it requires significant manual management for scaling and deployments, which goes against HipLocal's goals.