Professional Cloud Developer Exam QuestionsBrowse all questions from this exam

Professional Cloud Developer Exam - Question 43


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's .net-based auth service fails under intermittent load.

What should they do?

Show Answer
Correct Answer: AD

Using App Engine provides autoscaling and supports .NET applications, meeting the requirements for a serverless architecture that facilitates elastic scaling. App Engine abstracts infrastructure management, aligns with Google's best practices for cloud computing, and enhances uptime monitoring capabilities. These features ensure the application can scale smoothly to meet global demand and handle increased concurrent users, while also offering flexibility to deploy in multiple regions with proper configuration.

Discussion

17 comments
Sign in to comment
saurabh1805Option: A
Nov 9, 2020

A is correct answer here App engine, as app engine flexible support .net

fraloca
Dec 24, 2020

A is wrong because appengine is single region: https://cloud.google.com/appengine/docs/locations. For me the correct answer is C, compute engine with instance Group.

donchick
Jan 2, 2021

One of reqs is "Move to serverless architecture to facilitate elastic scaling". I vote for A.

StelSen
Feb 24, 2021

A is correct

gfr892Option: C
Jan 22, 2022

App Engine is regional. C is correct, because is the only multi-regional solution

akshaychavan7Option: C
Jul 5, 2022

Initially, I had picked option A considering the flexible request support. However, it imposes the limitation of a single region which is not expected in the case study. So, the only suitable option here is to use Compute Engine Cluster.

akshaychavan7
Aug 3, 2022

Also, note that "Existing APIs run on Compute Engine virtual machine instances hosted in Google Cloud", which is given in the existing technical environment. Considering this, it is advisable that instead of using a single VM we can create a cluster of such VMs and distribute the load among them.

RajanOption: B
Sep 24, 2023

B is correct.

santoshchauhanOption: B
Mar 7, 2024

B. Use Cloud Functions for autoscaling: Cloud Functions is a serverless execution environment that automatically scales based on the load. It is well-suited for applications with intermittent or unpredictable traffic patterns, such as HipLocal's auth service. The serverless nature of Cloud Functions also reduces infrastructure management overhead, aligning with the business requirement to reduce management time and cost. However, it's important to note that the runtime support for .NET in Cloud Functions is limited, and a migration or use of an alternative supported runtime might be necessary.

nehaxlpbOption: A
Jul 26, 2022

A is correct answer here App engine, as app engine flexible support .net

kinoko1330Option: A
Aug 20, 2022

A for "serverless architecture to facilitate elastic scaling"

tomato123Option: A
Aug 20, 2022

A is correct

telpOption: C
Jan 13, 2023

C is correct because app engine is regional only so it not answer the need of global application

FoxalOption: C
Feb 2, 2023

C is correct, A option is for regional solutions

edward_zhangOption: A
Feb 20, 2023

I vote A. App Engine cannot run in multi-region. But we can create multiple projects for supporting different region app engine.

minagmaxwellOption: A
Jul 13, 2023

A is correct. Don't get thrown off by app engine being regional. Google has demonstracted you can deploy to multiple regions by creating multiple project and throwing a load balancer in front. Check their demo toward the end: https://www.youtube.com/watch?v=JCvzUTmKakQ&ab_channel=GoogleCloudTech

RajanOption: C
Sep 19, 2023

Option C is correct as AppEngine is regional.

Rajan
Sep 24, 2023

I would go with Option B Cloud Function. Since it is a global resource and is scalable on demand.

wanrltw
Nov 18, 2023

Cloud Functions isn't an optimal solution for an entire app.

xiaofeng_0226Option: B
Nov 9, 2023

Vote for B

wanrltwOption: A
Nov 18, 2023

Serverless architecture -> App Engine

AeglasOption: A
Nov 25, 2023

A, since AppEngine can be deployed in several regions with a Load Balancer in front as demonstrated by Google. This will make the deployment serverless as requested, sticking to .net framework.

thewalkerOption: B
Jul 17, 2024

The best answer here is B. Use Cloud Functions for autoscaling. Here's why: Serverless Architecture: Cloud Functions is a serverless platform, meaning you don't need to manage servers or infrastructure. This aligns with the technical requirement to move to a serverless architecture for elastic scaling. Autoscaling: Cloud Functions automatically scales based on demand, ensuring that your auth service can handle spikes in traffic without performance degradation. This addresses the business requirement of increasing the number of concurrent users. Cost-Effective: Serverless platforms like Cloud Functions are cost-effective because you only pay for the resources you use. This aligns with the business requirement of reducing infrastructure management time and cost. Improved Reliability: Cloud Functions is a highly reliable platform, reducing the risk of downtime and improving the user experience. This addresses the business requirement of ensuring a consistent experience for users.

thewalker
Jul 17, 2024

Why other options are less suitable: A. Use App Engine for autoscaling: While App Engine is a good option for autoscaling, it's not as ideal for a specific service like authentication. Cloud Functions is more lightweight and focused on individual functions. C. Use a Compute Engine cluster for the service: This approach requires more manual management and configuration, making it less efficient and cost-effective than Cloud Functions. D. Use a dedicated Compute Engine virtual machine instance for the service: This is the least scalable option and doesn't address the issue of intermittent load. In summary: Cloud Functions provides the best combination of autoscaling, serverless architecture, cost-effectiveness, and reliability to address HipLocal's challenges with their .NET-based auth service.