Your Dataproc cluster runs in a single Virtual Private Cloud (VPC) network in a single subnet with range
172.16.20.128/25. There are no private IP addresses available in the VPC network. You want to add new VMs to communicate with your cluster using the minimum number of steps. What should you do?

• A.Modify the existing subnet range to 172.16.20.0/24.
• B.Create a new Secondary IP Range in the VPC and configure the VMs to use that range.
• C.Create a new VPC network for the VMs. Enable VPC Peering between the VMs' VPC network and the Dataproc cluster VPC network.
• D.Create a new VPC network for the VMs with a subnet of 172.32.0.0/16. Enable VPC network Peering between the Dataproc VPC network and the VMs VPC network. Configure a custom Route exchange.

Comment: *

Name: *

Email: *

Verification: *

You are working for a hospital that stores its medical images in an on-premises data room. The hospital wants to use Cloud Storage for archival storage of these images. The hospital wants an automated process to upload any new medical images to Cloud Storage. You need to design and implement a solution. What should you do?

• A.Create a Pub/Sub topic, and enable a Cloud Storage trigger for the Pub/Sub topic. Create an application that sends all medical images to the Pub/Sub topic.
• B.Deploy a Dataflow job from the batch template, "Datastore to Cloud Storage." Schedule the batch job on the desired interval.
• C.In the Cloud Console, go to Cloud Storage. Upload the relevant images to the appropriate bucket.
• D.Create a script that uses the gsutilcommand line interface to synchronize the on-premises storage with Cloud Storage. Schedule the script as a cron job.

Comment: *

Name: *

Email: *

Verification: *

You are hosting an application from Compute Engine virtual machines (VMs) in us-central1-a.
You want to adjust your design to support the failure of a single Compute Engine zone, eliminate downtime, and minimize cost. What should you do?

• A.- Create Compute Engine resources in us-central1-b.
  - Balance the load across both us-central1-a and us-central1-b.
• B.- Create a Managed Instance Group and specify us-central1-a as the zone.
  - Configure the Health Check with a short Health Interval.
• C.- Create an HTTP(S) Load Balancer.
  - Create one or more global forwarding rules to direct traffic to your VMs.
• D.- Perform regular backups of your application.
  - Create a Cloud Monitoring Alert and be notified if your application becomes unavailable.
  - Restore from backups when notified.

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
  * Source filter: IP ranges (with the range set to 10.0.2.0/24)
  * Protocols: allow all
  2. 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
• B.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:8080
  2. 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
• 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: 8080
  2. 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 all
  2. 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: *

You are given a project with a single virtual private cloud (VPC) and a single subnetwork in the us-central1 region. There is a Compute Engine instance hosting an application in this subnetwork. You need to deploy a new instance in the same project in the europe-west1 region. This new instance needs access to the application.
You want to follow Google-recommended practices. What should you do?

• A.1. Create a VPC and a subnetwork in europe-west1.2. Peer the 2 VPCs.3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.
• B.1. Create a subnetwork in the same VPC, in europe-west1.2. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.
• C.1. Create a subnetwork in the same VPC, in europe-west1.2. Use Cloud VPN to connect the two subnetworks.3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.
• D.1. Create a VPC and a subnetwork in europe-west1.2. Expose the application with an internal load balancer.3. Create the new instance in the new subnetwork and use the load balancer's address as the endpoint.

Comment: *

Name: *

Email: *

Verification: *