You are writing a single-page web application with a user-interface that communicates with a third-party API for content using XMLHttpRequest. The data displayed on the UI by the API results is less critical than other data displayed on the same web page, so it is acceptable for some requests to not have the API data displayed in the UI. However, calls made to the API should not delay rendering of other parts of the user interface. You want your application to perform well when the API response is an error or a timeout.
What should you do?

• A.Set the asynchronous option for your requests to the API to false and omit the widget displaying the API results when a timeout or error is encountered.
• B.Set the asynchronous option for your request to the API to true and omit the widget displaying the API results when a timeout or error is encountered.
• C.Catch timeout or error exceptions from the API call and keep trying with exponential backoff until the API response is successful.
• D.Catch timeout or error exceptions from the API call and display the error response in the UI widget.

Comment: *

Name: *

Email: *

Verification: *

Your application is running as a container in a Google Kubernetes Engine cluster. You need to add a secret to your application using a secure approach. What should you do?

• A.Create a Kubernetes Secret, and pass the Secret as an environment variable to the container.
• B.Enable Application-layer Secret Encryption on the cluster using a Cloud Key Management Service (KMS) key.
• C.Store the credential in Cloud KMS. Create a Google service account (GSA) to read the credential from Cloud KMS. Export the GSA as a .json file, and pass the .json file to the container as a volume which can read the credential from Cloud KMS.
• D.Store the credential in Secret Manager. Create a Google service account (GSA) to read the credential from Secret Manager. Create a Kubernetes service account (KSA) to run the container.Use Workload Identity to configure your KSA to act as a GSA.

Comment: *

Name: *

Email: *

Verification: *

You are a developer at a social media company The company runs their social media website on-premises and uses MySQL as a backend to store user profiles and user posts. Your company plans to migrate to Google Cloud, and your team will migrate user profile information to Firestore. You are tasked with designing the Firestore collections. What should you do?

• A.Create one root collection for user profiles, and store each user's post as a nested list in the user profile document.
• B.Create one root collection for user posts, and create one subcollection for each user's profile
• C.Create one root collection for user profiles, and create one root collection for user posts.
• D.Create one root collection for user profiles, and create one subcollection for each user's posts.

Comment: *

Name: *

Email: *

Verification: *

You are developing a new application. You want the application to be triggered only when a given file is updated in your Cloud Storage bucket. Your trigger might change, so your process must support different types of triggers. You want the configuration to be simple so that multiple team members can update the triggers in the future. What should you do?

• A.Configure a Firebase function that executes your application and is triggered when an object is updated in Cloud Storage.
• B.Configure Cloud Storage events to be sent to Pub/Sub, and use Pub/Sub events to trigger a Cloud Build job that executes your application.
• C.Configure a Cloud Function that executes your application and is triggered when an object is updated in Cloud Storage.
• D.Create an Eventarc trigger that monitors your Cloud Storage bucket for a specific filename, and set the target as Cloud Run.

Comment: *

Name: *

Email: *

Verification: *

Case Study 2 - HipLocal
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, and that they analyze and respond to any issues that occur.
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.
- Release cycles include development freezes to allow for QA testing.
- The application has no logging.
- Applications are manually deployed by infrastructure engineers during periods of slow traffic on weekday evenings.
- 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.
- Support 10x as many concurrent users.
- 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.
Develop standardized workflows and processes around application lifecycle management.
Define service level indicators (SLIs) and service level objectives (SLOs).
Technical Requirements
- Provide secure communications between the on-premises data center and cloud-hosted applications and infrastructure.
- The application must provide usage metrics and monitoring.
- APIs require authentication and authorization.
- Implement faster and more accurate validation of new features.
- Logging and performance metrics must provide actionable information to be able to provide debugging information and alerts.
- Must scale to meet user demand.
For this question, refer to the HipLocal case study.
How should HipLocal redesign their architecture to ensure that the application scales to support a large increase in users?

• A.Use Google Kubernetes Engine (GKE) to run the application as a microservice. Run the MySQL database on a dedicated GKE node.
• B.Use multiple Compute Engine instances to run MySQL to store state information. Use a Google Cloud-managed load balancer to distribute the load between instances. Use managed instance groups for scaling.
• C.Use Memorystore to store session information and CloudSQL to store state information. Use a Google Cloud-managed load balancer to distribute the load between instances. Use managed instance groups for scaling.
• D.Use a Cloud Storage bucket to serve the application as a static website, and use another Cloud Storage bucket to store user state information.

Comment: *

Name: *

Email: *

Verification: *