You are designing an application that shares PDF files containing time-sensitive information with users. The PDF files are saved in Cloud Storage. You need to provide secure access to the files.
You have the following requirements:
- Users should only have access to files that they are allowed to view.
- Users should be able to request to read, write, or delete the PDF
files for 24 hours.
Not all users of the application have a Google account. How should you provide access to data objects?

• A. Generate a service account that grants access to the POF files. Configure the application to provide users with a download link to the service account's key file. Set an expiration time of 24 hours to the service account Keys. Instruct users to authenticate by using the service account key file.
• B. Provide users with the Service Account Token Creator IAM role to impersonate the application's service account. Assign the Cloud Storage User IAM role to the application's service account to access the Cloud Storage bucket. Rotate the application's service account key every 24 hours.
• C. Configure the application to generate signed URLs with an expiration time of 24 hours. Share the signed URLs with users. Attach the signed URL to the PDF files that users require access to.
• D. Assign the Storage Object User IAM role to users that request access to the PDF files. Set an IAM condition on the role to expire after 24 hours.

You are designing an application that will subscribe to and receive messages from a single Pub/Sub topic and insert corresponding rows into a database. Your application runs on Linux and leverages preemptible virtual machines to reduce costs. You need to create a shutdown script that will initiate a graceful shutdown.
What should you do?

• A. Write a shutdown script that publishes a message to the Pub/Sub topic announcing that a shutdown is in progress. After the application reads the message, it disconnects from the database.
• B. Write a shutdown script that writes a file in a location that is being polled by the application once every five minutes. After the file is read, the application disconnects from the database.
• C. Write a shutdown script that broadcasts a message to all signed-in users that the Compute Engine instance is going down and instructs them to save current work and sign out.
• D. Write a shutdown script that uses inter-process signals to notify the application process to disconnect from the database.

Your company plans to expand their analytics use cases. One of the new use cases requires your data analysts to analyze events using SQL on a near real-time basis. You expect rapid growth and want to use managed services as much as possible. What should you do?

• A. Create a Cloud Pub/Sub topic and a subscription. Stream your events from the source into the Pub/Sub topic. Leverage Cloud Dataflow to ingest these events into Cloud Storage.
• B. Create a Cloud Pub/Sub topic and a subscription. Stream your events from the source into the Pub/Sub topic. Leverage Cloud Dataflow to ingest these events into Cloud Datastore.
• C. Create a Kafka instance on a large Compute Engine instance. Stream your events from the source into a Kafka pipeline. Leverage Cloud Dataflow to ingest these events into Cloud Storage.
• D. Create a Cloud Pub/Sub topic and a subscription. Stream your events from the source into the Pub/Sub topic. Leverage Cloud Dataflow to ingest these events into BigQuery.

You are developing an application component to capture user behavior data and stream the data to BigQuery. You plan to use the BigQuery Storage Write API. You need to ensure that the data that arrives in BigQuery does not have any duplicates. You want to use the simplest operational method to achieve this. What should you do?

• A. Create a write stream in the committed type.
• B. Configure a Pub/Sub topic. Use Cloud Run functions to subscribe to the topic and remove any duplicates.
• C. Create a write stream in the default type.
• D. Configure a Kafka cluster. Use a primary universally unique identifier (UUID) for duplicate messages.

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.
HipLocal's application uses Cloud Client Libraries to interact with Google Cloud. HipLocal needs to configure authentication and authorization in the Cloud Client Libraries to implement least privileged access for the application. What should they do?

• A. Use the default compute service account to interact with Google Cloud.
• B. Create an API key. Use the API key to interact with Google Cloud.
• C. Create a service account for the application and for each Google Cloud API used by the application. Export and deploy the private keys used by the application. Use the service account with one Google Cloud API to interact with Google Cloud.
• D. Create a service account for the application. Export and deploy the private key for the application.
  Use the service account to interact with Google Cloud.