Here you have the best Google Professional Cloud Developer practice exam questions
You want to upload files from an on-premises virtual machine to Google Cloud Storage as part of a data migration. These files will be consumed by Cloud
DataProc Hadoop cluster in a GCP environment.
Which command should you use?
To upload files from an on-premises virtual machine to Google Cloud Storage, the correct command to use is 'gsutil cp'. The 'gsutil' command is specifically designed for interacting with Google Cloud Storage and 'cp' is the sub-command used to copy files. The other command options, such as 'gcloud cp' or 'hadoop fs cp', are either incorrect or not intended for this specific purpose. 'gcloud dataproc' is related to managing Cloud Dataproc clusters but not for file transfers to Cloud Storage.
You migrated your applications to Google Cloud Platform and kept your existing monitoring platform. You now find that your notification system is too slow for time critical problems.
What should you do?
To address the issue of slow notification for critical problems after migrating to Google Cloud Platform, you should use Stackdriver to capture and alert on logs, then ship them to your existing platform. This allows you to leverage Stackdriver's real-time alerting capabilities while maintaining your current monitoring system for in-depth analysis and storage. Replacing your entire monitoring platform or installing Stackdriver agents alone would not directly address the notification delay, and migrating traffic back for A/B testing is unrelated to solving the notification speed problem.
You are planning to migrate a MySQL database to the managed Cloud SQL database for Google Cloud. You have Compute Engine virtual machine instances that will connect with this Cloud SQL instance. You do not want to whitelist IPs for the Compute Engine instances to be able to access Cloud SQL.
What should you do?
To enable Compute Engine instances to access a Cloud SQL instance without whitelisting IPs, enabling private IP for the Cloud SQL instance is the best approach. Private IP allows the instances and the Cloud SQL instance to communicate over a private, internal network within Google Cloud Platform (GCP), avoiding exposure to the public internet and eliminating the need for IP whitelisting. This method ensures secure, internal communication and simplifies network configuration.
You have deployed an HTTP(s) Load Balancer with the gcloud commands shown below.
Health checks to port 80 on the Compute Engine virtual machine instance are failing and no traffic is sent to your instances. You want to resolve the problem.
Which commands should you run?
To resolve the problem with health checks failing on port 80, you need to allow incoming traffic for the health check probes from the IP ranges used by Google Cloud Load Balancers. The correct command is to create an ingress firewall rule that permits TCP traffic from these source IP ranges (130.211.0.0/22 and 35.191.0.0/16). This will enable the load balancer's health check to reach the instances and verify their status, ensuring proper traffic routing.
Your website is deployed on Compute Engine. Your marketing team wants to test conversion rates between 3 different website designs.
Which approach should you use?
To test conversion rates between 3 different website designs, you should deploy the website on App Engine and use traffic splitting. App Engine's traffic splitting feature allows you to distribute traffic across different versions of your application. This is particularly useful for A/B testing scenarios, as it seamlessly directs a specified percentage of users to different versions of your website. This setup provides a controlled environment for the marketing team to analyze the impact of each design on conversion rates without changing the domain or requiring separate URLs.