PCA-3

You are migrating your on-premises solution to Google Cloud in several phases. You will use Cloud VPN to maintain a connection between your on-premises systems and Google Cloud until the migration is completed. You want to make sure all your on-premise systems remain reachable during this period. How should you organize your networking in Google Cloud?

•   Use the same IP range on Google Cloud as you use on-premises

• Use the same IP range on Google Cloud as you use on-premises for your primary IP range and use a secondary range that does not overlap with the range you use on-premises

• Use an IP range on Google Cloud that does not overlap with the range you use on-premises

• Use an IP range on Google Cloud that does not overlap with the range you use on-premises for your primary IP range and use a secondary range with the same IP range as you use on-premises

You have found an error in your App Engine application caused by missing Cloud Datastore indexes. You have created a YAML file with the required indexes and want to deploy these new indexes to Cloud Datastore. What should you do?

• Point gcloud datastore create-indexes to your configuration file

• Upload the configuration file to App Engine’s default Cloud Storage bucket, and have App Engine detect the new indexes

• In the GCP Console, use Datastore Admin to delete the current indexes and upload the new configuration file

•  

    Create an HTTP request to the built-in python module to send the index configuration file to your application

You have an application that will run on Compute Engine. You need to design an architecture that takes into account a disaster recovery plan that requires your application to fail over to another region in case of a regional outage. What should you do?

• Deploy the application on two Compute Engine instances in the same project but in a different region. Use the first instance to serve traffic, and use the HTTP load balancing service to fail over to the standby instance in case of a disaster.

• Deploy the application on a Compute Engine instance. Use the instance to serve traffic, and use the HTTP load balancing service to fail over to an instance on your premises in case of a disaster.

• Deploy the application on two Compute Engine instance groups, each in the same project but in a different region. Use the first instance group to serve traffic, and use the HTTP load balancing service to fail over to the standby instance group in case of a disaster.

• Deploy the application on two Compute Engine instance groups, each in a separate project and a different region. Use the first instance group to serve traffic, and use the HTTP load balancing service to fail over to the standby instance group in case of a disaster.

You are deploying an application on App Engine that needs to integrate with an on-premises database. For security purposes, your on-premises database must not be accessible through the public internet. What should you do?

• Deploy your application on App Engine standard environment and use App Engine firewall rules to limit access to the open on-premises database.

•   Deploy your application on App Engine standard environment and use Cloud VPN to limit access to the on-premises database.

•   Deploy your application on App Engine flexible environment and use App Engine firewall rules to limit access to the on- premises database.

• Deploy your application on App Engine flexible environment and use Cloud VPN to limit access to the on-premises database.

You are working in a highly secured environment where public Internet access from the Compute Engine VMs is not allowed. You do not yet have a VPN connection to access an on-premises file server. You need to install specific software on a Compute Engine instance. How should you install the software?

• Upload the required installation files to Cloud Storage. Configure the VM on a subnet with a Private Google Access subnet. Assign only an internal IP address to the VM. Download the installation files to the VM using gsutil.

• Upload the required installation files to Cloud Storage and use firewall rules to block all traffic except the IP address range for Cloud Storage. Download the files to the VM using gsutil.

• Upload the required installation files to Cloud Source Repositories. Configure the VM on a subnet with a Private Google Access subnet. Assign only an internal IP address to the VM. Download the installation files to the VM using gcloud.

• Upload the required installation files to Cloud Source Repositories and use firewall rules to block all traffic except the IP address range for Cloud Source Repositories. Download the files to the VM using gsutil.

Your company is moving 75 TB of data into Google Cloud. You want to use Cloud Storage and follow Google-recommended practices. What should you do?

• Move your data onto a Transfer Appliance. Use a Transfer Appliance Rehydrator to decrypt the data into Cloud Storage.

•   Move your data onto a Transfer Appliance. Use Cloud Dataprep to decrypt the data into Cloud Storage.

•  

  Install gsutil on each server that contains data. Use resumable transfers to upload the data into Cloud Storage.

• Install gsutil on each server containing data. Use streaming transfers to upload the data into Cloud Storage.

You have an application deployed on Google Kubernetes Engine using a Deployment named echo-deployment. The deployment is exposed using a Service called echo-service. You need to perform an update to the application with minimal downtime to the application. What should you do?

• Use kubectl set image deployment/echo-deployment

• Use the rolling update functionality of the Instance Group behind the Kubernetes cluster

• Update the deployment yaml file with the new container image. Use kubectl delete deployment/echo-deployment and kubectl create –f

• Update the service yaml file which the new container image. Use kubectl delete service/echo-service and kubectl create – f

Your company is using BigQuery as its enterprise data warehouse. Data is distributed over several Google Cloud projects. All queries on BigQuery need to be billed on a single project. You want to make sure that no query costs are incurred on the projects that contain the data. Users should be able to query the datasets, but not edit them. How should you configure users’ access roles?

• Add all users to a group. Grant the group the role of BigQuery user on the billing project and BigQuery dataViewer on the projects that contain the data.

• Add all users to a group. Grant the group the roles of BigQuery dataViewer on the billing project and BigQuery user on the projects that contain the data.

• Add all users to a group. Grant the group the roles of BigQuery jobUser on the billing project and BigQuery dataViewer on the projects that contain the data.

• Add all users to a group. Grant the group the roles of BigQuery dataViewer on the billing project and BigQuery jobUser on the projects that contain the data.

You have developed an application using Cloud ML Engine that recognizes famous paintings from uploaded images. You want to test the application and allow specific people to upload images for the next 24 hours. Not all users have a Google Account. How should you have users upload images?

• Have users upload the images to Cloud Storage. Protect the bucket with a password that expires after 24 hours.

• Have users upload the images to Cloud Storage using a signed URL that expires after 24 hours.

• Create an App Engine web application where users can upload images. Configure App Engine to disable the application after 24 hours. Authenticate users via Cloud Identity.

• Create an App Engine web application where users can upload images for the next 24 hours. Authenticate users via Cloud Identity.

Your web application must comply with the requirements of the European Union’s General Data Protection Regulation (GDPR). You are responsible for the technical architecture of your web application. What should you do?

•   Ensure that your web application only uses native features and services of Google Cloud Platform, because Google already has various certifications and provides “pass-on” compliance when you use native features.

• Enable the relevant GDPR compliance setting within the GCPConsole for each of the services in use within your application.

• Ensure that Cloud Security Scanner is part of your test planning strategy in order to pick up any compliance gaps.

• Define a design for the security of data in your web application that meets GDPR requirements.