You have a Compute Engine instance hosting an application used between 9 AM and 6 PM on weekdays. You want to back up this instance daily for disaster recovery purposes. You want to keep the backups for 30 days. You want the Google-recommended solution with the least management overhead and the least number of services. What should you do?

• A.1. Create a bash script in the instance that copies the content of the disk to Cloud Storage.
  2. Create a bash script in the instance that deletes data older than 30 days in the backup Cloud Storage bucket.
  3. Configure the instance's crontab to execute these scripts daily at 1:00 AM.
• B.1. In the Cloud Console, go to the Compute Engine Disks page and select your instance's disk.
  2. In the Snapshot Schedule section, select Create Schedule and configure the following parameters:
  - Schedule frequency: Daily
  - Start time: 1:00 AM - 2:00 AM
  - Autodelete snapshots after 30 days
• C.1. Update your instances' metadata to add the following value: snapshot-schedule: 0 1 * * *
  2. Update your instances' metadata to add the following value: snapshot-retention: 30
• D.1. Create a Cloud Function that creates a snapshot of your instance's disk.
  2. Create a Cloud Function that deletes snapshots that are older than 30 days.
  3. Use Cloud Scheduler to trigger both Cloud Functions daily at 1:00 AM.

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 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
• 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 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
• 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 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: *

You have downloaded and installed the gcloud command line interface (CLI) and have authenticated with your Google Account. Most of your Compute Engine instances in your project run in the europe-west1-d zone. You want to avoid having to specify this zone with each CLI command when managing these instances. What should you do?

• A.Create a Metadata entry on the Compute Engine page with key compute/zone and value europe-west1-d.
• B.In the CLI installation directory, create a file called default.conf containing zone=europe-west1-d.
• C.Set the europe-west1-d zone as the default zone using the gcloud config subcommand.
• D.In the Settings page for Compute Engine under Default location, set the zone to europe-west1-d.

Comment: *

Name: *

Email: *

Verification: *

You need to verify that a Google Cloud Platform service account was created at a particular time.
What should you do?

• A.Filter the Activity log to view the Data Access category. Filter the Resource type to Google Project.
• B.Filter the Activity log to view the Configuration category. Filter the Resource type to Google Project.
• C.Filter the Activity log to view the Configuration category. Filter the Resource type to Service Account.
• D.Filter the Activity log to view the Data Access category. Filter the Resource type to Service Account.

Comment: *

Name: *

Email: *

Verification: *