Professional-Cloud-Architect 無料問題集「Google Certified Professional - Cloud Architect (GCP)」

（A）Create a dump of the MySQL replica server into the cloud environment, load it into: Google Cloud Datastore, and configure applications to read/write to Cloud Datastore at cutover.

（B）Create a dump of the on-premises MySQL master server, and then shut it down, upload it to the cloud environment, and load into a new MySQL cluster.

（C）Setup a MySQL replica server/slave in the cloud environment, and configure it for asynchronous replication from the MySQL master server on-premises until cutover.

（D）Create a new MySQL cluster in the cloud, configure applications to begin writing to both on-premises and cloud MySQL masters, and destroy the original cluster at cutover.

（A）Navigate the predefined dashboards in the Cloud Monitoring workspace, create custom metrics, and install alerting software on a Compute Engine instance.

（B）Create a custom dashboard in the Cloud Monitoring workspace for each incident, and then add metrics and create alert policies.

（C）Navigate the predefined dashboards in the Cloud Monitoring workspace, and then add metrics and create alert policies.

（D）Write a shell script that gathers metrics from GKE nodes, publish these metrics to a Pub/Sub topic, export the data to BigQuery, and make a Data Studio dashboard.

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

（B）Use a private cluster with a private endpoint with master authorized networks configured.

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

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

（A）Restore a backup of the application database from a time before the application became slow.

（B）Change the Compute Engine Instances behind the application to a machine type with more CPU and memory.

（C）Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.

（D）Deploy the applications on a managed instance group with autoscaling enabled. Add a load balancer in front of the managed instance group, and have the users connect to the IP of the load balancer.

（A）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

（B）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

（C）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

（D）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

（A）Cloud Pub/Sub to Cloud DataFlow

（B）Cloud Pub/Sub to Cloud SQL

（C）Cloud Pub/Sub alone

（D）Cloud Pub/Sub to Stackdriver

（A）The effective policy is the intersection of the policy set at the node and policies inherited from its ancestors

（B）The effective policy is determined only by the policy set at the node

（C）The effective policy is the union of the policy set at the node and policies inherited from its ancestors

（D）The effective policy is the policy set at the node and restricted by the policies of its ancestors

（A）Store static content such as HTML and images in Cloud CDN. Host the APIs on App Engine and store the user data in Cloud SQL.

（B）Store static content such as HTML and images in Cloud CDN. Use Cloud Run to host the APIs and save the user data in Cloud SQL.

（C）Store static content such as HTML and images in a Cloud Storage bucket. Host the APIs on a zonal Google Kubernetes Engine cluster with worker nodes in multiple zones, and save the user data in Cloud Spanner.

（D）Store static content such as HTML and images in a Cloud Storage bucket. Use Cloud Functions to host the APIs and save the user data in Firestore.

（A）Use a versioning strategy for the APIs that increases the version number on every backward-incompatible change.

（B）Create a distribution list of all customers to inform them of an upcoming backward-incompatible change at least one month before replacing the old API with the new API.

（C）Use a versioning strategy for the APIs that adds the suffix "DEPRECATED" to the current API version number on every backward-incompatible change. Use the current version number for the new API.

（D）Create an automated process to generate API documentation, and update the public API documentation as part of the CI/CD process when deploying an update to the API.

（A）Use automated scripts to automate service provisioning. Use Activity Logs monitor and debug your tests.

（B）Use Deployment Manager to automate provisioning. Use Stackdriver to monitor and debug your tests.

（C）Use Deployment Manager to automate service provisioning. Use Activity Logs to monitor and debug your tests.

（D）Use gcloud scripts to automate service provisioning. Use Activity Logs monitor and debug your tests.

（A）Compute Engine

（B）Cloud Endpoints

（C）Google Kubernetes Engine

（D）App Engine

（A）Set up Identity and Access Management (IAM) and Confidential Computing to trigger a Cloud Function.

（B）Set up Cloud Tasks and a Cloud Storage bucket that triggers a Cloud Function.

（C）Set up a Cloud Logging sink and a Cloud Storage bucket that triggers a Cloud Function.

（D）Configure the deployment job to notify a Pub/Sub queue that triggers a Cloud Function.

（A）Update the existing Kubernetes Engine cluster with the following command:gcloud alpha container clustersupdate mycluster - -enable-autoscaling - -min-nodes=1 - -max-nodes=10

（B）Add additional nodes to your Kubernetes Engine cluster using the following command:gcloud container clusters resizeCLUSTER_Name - -size 10

（C）Add a tag to the instances in the cluster with the following command:gcloud compute instances add-tagsINSTANCE - -tags enable-autoscaling max-nodes-10

（D）Create a new Kubernetes Engine cluster with the following command:gcloud alpha container clusterscreate mycluster - -enable-autoscaling - -min-nodes=1 - -max-nodes=10and redeploy your application

（A）Make sure there are no other users consuming the 1 Gbps link, and use multi-thread transfer to upload the data to Cloud Storage.

（B）Configure the Storage Transfer service from Google Cloud to send the data from your data center to Cloud Storage

（C）Request Transfer Appliances from Google Cloud, export the data to appliances, and return the appliances to Google Cloud.

（D）Export files to an encrypted USB device, send the device to Google Cloud, and request an import of the data to Cloud Storage

（A）Use gsutil to upload the files, and use the flag --encryption-key to supply the encryption key.

（B）Supply the encryption key in a .boto configuration file. Use gsutil to upload the files.

（C）Use gsutil to create a bucket, and use the flag --encryption-key to supply the encryption key. Use gsutil to upload the files to that bucket.

（D）Supply the encryption key using gcloud config. Use gsutil to upload the files to that bucket.

（A）Create a Compute engine instance with CPU and Memory options similar to your application's current on-premises virtual machine. Install the cloud monitoring agent, and deploy the third party application.
Run a load with normal traffic levels on third party application and follow the Rightsizing Recommendations in the Cloud Console

（B）Create multiple Compute Engine instances with varying CPU and memory options. Install the cloud monitoring agent and deploy the third-party application on each of them. Run a load test with high traffic levels on the application and use the results to determine the optimal settings.

（C）Create an App Engine flexible environment, and deploy the third party application using a Docker file and a custom runtime. Set CPU and memory options similar to your application's current on-premises virtual machine in the app.yaml file.

（D）Create an instance template with the smallest available machine type, and use an image of the third party application taken from the current on-premises virtual machine. Create a managed instance group that uses average CPU to autoscale the number of instances in the group. Modify the average CPU utilization threshold to optimize the number of instances running.