Pass the Google Cloud Certified Professional-Cloud-Architect Questions and answers with ExamsMirror

1) Use gsutil -m to upload all the files to Cloud Storage.

2) Use gsutil cp to download the uploaded files

3) Use Linux diff to compare the content of the files

1) Use gsutil -m to upload all the files to Cloud Storage.

2) Develop a custom Java application that computes CRC32C hashes

3) Use gsutil ls -L gs://[YOUR_BUCKET_NAME] to collect CRC32C hashes of the uploaded files

4)Compare the hashes

1) Use Linux shasum to compute a digest of files you want to upload

2) Use gsutil -m to upload all the files to the Cloud Storage

3) Use gsutil cp to download the uploaded files

4) Use Linux shasum to compute a digest of the downloaded files 5.Compre the hashes

1)Use gsutil -m to upload all the files to Cloud Storage.

2)Use gsutil hash -c FILE_NAME to generate CRC32C hashes of all on-premises files

3)Use gsutil ls -L gs://[YOUR_BUCKET_NAME] to collect CRC32C hashes of the uploaded files

4)Compare the hashes

Set up a filter in Cloud Logging and a topic in Pub/Sub to publish the logs

Set up a Cloud Logging Dashboard titled Cloud VPN Logs, and then add a chart that queries for the VPN metrics over a one-year time period

Enable the Compute Engine API and then enable logging on the firewall rules that match the traffic you want to save

Set up a filter in Cloud Logging and a Cloud Storage bucket as an export target for the logs you want to save

Create a Cloud VPN connection from the new VPC to the data center, create a Cloud Router, and apply new IP addresses so there is no overlapping IP space.

Create a Cloud VPN connection from the new VPC to the data center, and create a Cloud NAT instance to perform NAT on the overlapping IP space.

Create a Cloud VPN connection from the new VPC to the data center, create a Cloud Router, and apply a custom route advertisement to block the overlapping IP space.

Create a Cloud VPN connection from the new VPC to the data center, and apply a firewall rule that blocks the overlapping IP space.

Bucket Lock

Object Versioning

Object change notification

Object Lifecycle Management

Work with your ISP to diagnose the problem.

Open a support ticket to ask for network capture and flow data to diagnose the problem, then roll back your application.

Roll back to an earlier known good release initially, then use Stackdriver Trace and logging to diagnose the problem in a development/test/staging environment.

Roll back to an earlier known good release, then push the release again at a quieter period to investigate. Then use Stackdriver Trace and logging to diagnose the problem.

Verify EHR's product usage against the list of compliant products on the Google Cloud compliance page.

Advise EHR to execute a Business Associate Agreement (BAA) with Google Cloud.

Use Firebase Authentication for EHR's user facing applications.

Implement Prometheus to detect and prevent security breaches on EHR's web-based applications.

Use GKE private clusters for all Kubernetes workloads.

Add a new Dedicated Interconnect connection

Upgrade the bandwidth on the Dedicated Interconnect connection to 100 G

Add three new Cloud VPN connections

Add a new Carrier Peering connection

Enable Binary Authorization on GKE, and sign containers as part of a CI/CD pipeline.

Configure Jenkins to utilize Kritis to cryptographically sign a container as part of a CI/CD pipeline.

Configure Container Registry to only allow trusted service accounts to create and deploy containers from the registry.

Configure Container Registry to use vulnerability scanning to confirm that there are no vulnerabilities before deploying the workload.

Add a new Dedicated Interconnect connection.

Upgrade the bandwidth on the Dedicated Interconnect connection to 100 G.

Add three new Cloud VPN connections.

Add a new Carrier Peering connection.

Use a private cluster with a private endpoint with master authorized networks configured.

Use a public cluster with firewall rules and Virtual Private Cloud (VPC) routes.

Use a private cluster with a public endpoint with master authorized networks configured.

Use a public cluster with master authorized networks enabled and firewall rules.