Your company is moving from an on-premises environment to Google Cloud Platform (GCP). You have multiple development teams that use Cassandra environments as backend databases. They all need a development environment that is isolated from other Cassandra instances. You want to move to GCP quickly and with minimal support effort. What should you do?

• A.1. Build a Cassandra Compute Engine instance and take a snapshot of it.
  2. Use the snapshot to create instances for your developers.
• B.1. Build an instruction guide to install Cassandra on GCP.
  2. Make the instruction guide accessible to your developers.
• C.1. Advise your developers to go to Cloud Marketplace.
  2. Ask the developers to launch a Cassandra image for their development work.
• D.1. Build a Cassandra Compute Engine instance and take a snapshot of it.
  2.Upload the snapshot to Cloud Storage and make it accessible to your developers.
  3.Build instructions to create a Compute Engine instance from the snapshot so that developers can do it themselves.

Comment: *

Name: *

Email: *

Verification: *

Your company has a 3-tier solution running on Compute Engine. The configuration of the current infrastructure is shown below.

Each tier has a service account that is associated with all instances within it. You need to enable communication on TCP port 8080 between tiers as follows:
* Instances in tier #1 must communicate with tier #2.
* Instances in tier #2 must communicate with tier #3.
What should you do?

• A.1. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #2 service account* Source filter: all instances with tier #1 service account* Protocols: allow TCP:80802. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #3 service account* Source filter: all instances with tier #2 service account* Protocols: allow TCP: 8080
• B.1. Create an ingress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.2.0/24)* Protocols: allow all2. Create an ingress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.1.0/24)* Protocols: allow all
• C.1. Create an egress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.2.0/24)* Protocols: allow TCP: 80802. Create an egress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.1.0/24)* Protocols: allow TCP: 8080
• D.1. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #2 service account* Source filter: all instances with tier #1 service account* Protocols: allow all2. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #3 service account* Source filter: all instances with tier #2 service account* Protocols: allow all

Comment: *

Name: *

Email: *

Verification: *

Your customer has implemented a solution that uses Cloud Spanner and notices some read latency-related performance issues on one table. This table is accessed only by their users using a primary key. The table schema is shown below.

You want to resolve the issue. What should you do?

• A.Create a secondary index using the following Data Definition Language (DDL):
  
• B.Remove the profile_picture field from the table.
• C.Add a secondary index on the person_id column.
• D.Change the primary key to not have monotonically increasing values.

Comment: *

Name: *

Email: *

Verification: *

You've deployed a microservice called myapp1 to a Google Kubernetes Engine cluster using the YAML file specified below:

You need to refactor this configuration so that the database password is not stored in plain text.
You want to follow Google-recommended practices. What should you do?

• A.Store the database password inside a Secret object.
  Modify the YAML file to populate the DB_PASSWORD environment variable from the Secret.
• B.Store the database password in a file inside a Kubernetes persistent volume, and use a persistent volume claim to mount the volume to the container.
• C.Store the database password inside the Docker image of the container, not in the YAML file.
• D.Store the database password inside a ConfigMap object.
  Modify the YAML file to populate the DB_PASSWORD environment variable from the ConfigMap.

Comment: *

Name: *

Email: *

Verification: *

Your company publishes large files on an Apache web server that runs on a Compute Engine instance. The Apache web server is not the only application running in the project. You want to receive an email when the egress network costs for the server exceed 100 dollars for the current month as measured by Google Cloud Platform (GCP). What should you do?

• A.Export the billing data to BigQuery. Create a Cloud Function that uses BigQuery to sum the egress network costs of the exported billing data for the Apache web server for the current month and sends an email if it is over 100 dollars. Schedule the Cloud Function using Cloud Scheduler to run hourly.
• B.Set up a budget alert on the billing account with an amount of 100 dollars, a threshold of 100%, and notification type of "email."
• C.Use the Stackdriver Logging Agent to export the Apache web server logs to Stackdriver Logging. Create a Cloud Function that uses BigQuery to parse the HTTP response log data in Stackdriver for the current month and sends an email if the size of all HTTP responses, multiplied by current GCP egress prices, totals over 100 dollars. Schedule the Cloud Function using Cloud Scheduler to run hourly.
• D.Set up a budget alert on the project with an amount of 100 dollars, a threshold of 100%, and notification type of "email."

Comment: *

Name: *

Email: *

Verification: *