For this question, refer to the TerramEarth case study.
To speed up data retrieval, more vehicles will be upgraded to cellular connections and be able to transmit data to the ETL process. The current FTP process is error-prone and restarts the data transfer from the start of the file when connections fail, which happens often. You want to improve the reliability of the solution and minimize data transfer time on the cellular connections. What should you do?

• A.Use one Google Container Engine cluster of FTP servers. Save the data to a Multi-Regional bucket. Run the ETL process using data in the bucket.
• B.Use multiple Google Container Engine clusters running FTP servers located in different regions. Save the data to Multi-Regional buckets in us, eu, and asia. Run the ETL process using the data in the bucket.
• C.Directly transfer the files to different Google Cloud Multi-Regional Storage bucket locations in us, eu, and asia using Google APIs over HTTP(S). Run the ETL process using the data in the bucket.
• D.Directly transfer the files to a different Google Cloud Regional Storage bucket location in us, eu, and asia using Google APIs over HTTP(S). Run the ETL process to retrieve the data from each Regional bucket.

Comment: *

Name: *

Email: *

Verification: *

Your organization has a 3-tier web application deployed in the same network on Google Cloud Platform. Each tier (web, API, and database) scales independently of the others Network traffic should flow through the web to the API tier and then on to the database tier. Traffic should not flow between the web and the database tier. How should you configure the network?

• A.Add each tier to a different subnetwork.
• B.Set up software based firewalls on individual VMs.
• C.Add tags to each tier and set up routes to allow the desired traffic flow.
• D.Add tags to each tier and set up firewall rules to allow the desired traffic flow.

Comment: *

Name: *

Email: *

Verification: *

You have created several preemptible Linux virtual machine instances using Google Compute Engine. You want to properly shut down your application before the virtual machines are preempted. What should you do?

• A.Create a shutdown script registered as a xinetd service in Linux and configure a Stackdnver endpoint check to call the service.
• B.Create a shutdown script and use it as the value for a new metadata entry with the key shutdown-script in the Cloud Platform Console when you create the new virtual machine instance.
• C.Create a shutdown script, registered as a xinetd service in Linux, and use the gcloud compute instances add-metadata command to specify the service URL as the value for a new metadata entry with the key shutdown-script-url
• D.Create a shutdown script named k99.shutdown in the /etc/rc.6.d/ directory.

Comment: *

Name: *

Email: *

Verification: *

The application reliability team at your company has added a debug feature to their backend service to send all server events to Google Cloud Storage for eventual analysis. The event records are at least 50 KB and at most 15 MB and are expected to peak at 3,000 events per second. You want to minimize data loss.
Which process should you implement?

• A.Append metadata to file body.
  Compress individual files.
  Name files with serverName-Timestamp.
  Create a new bucket if bucket is older than 1 hour and save individual files to the new bucket.
  Otherwise, save files to existing bucket
• B.Batch every 10,000 events with a single manifest file for metadata.
  Compress event files and manifest file into a single archive file.
  Name files using serverName-EventSequence.
  Create a new bucket if bucket is older than 1 day and save the single archive file to the new bucket. Otherwise, save the single archive file to existing bucket.
• C.Compress individual files.
  Name files with serverName-EventSequence.
  Save files to one bucket
  Set custom metadata headers for each object after saving.
• D.Append metadata to file body.
  Compress individual files.
  Name files with a random prefix pattern.
  Save files to one bucket

Comment: *

Name: *

Email: *

Verification: *

You are building a continuous deployment pipeline for a project stored in a Git source repository and want to ensure that code changes can be verified deploying to production. What should you do?

• A.Use Spinnaker to deploy builds to production using the red/black deployment strategy so that changes can easily be rolled back.
• B.Use Spinnaker to deploy builds to production and run tests on production deployments.
• C.Use Jenkins to build the staging branches and the master branch. Build and deploy changes to production for 10% of users before doing a complete rollout.
• D.Use Jenkins to monitor tags in the repository. Deploy staging tags to a staging environment for testing.
  After testing, tag the repository for production and deploy that to the production environment.

Comment: *

Name: *

Email: *

Verification: *