Associate-Cloud-Engineer 無料問題集「Google Associate Cloud Engineer」

（A）Set the maximum number of instances for your Cloud Run service to 100.

（B）Set the minimum number of instances for your Cloud Run service to 3.

（C）Update your web application to use the protocol HTTP/2 instead of HTTP/1.1

（D）Set the concurrency number to 1 for your Cloud Run service.

（A）Set up a proper billing account structure to group IAM policies

（B）Use labels to group resources that share common IAM policies

（C）Use folders to group resources that share common IAM policies

（D）Set up a proper project naming structure to group IAM policies

（A）Export users from Active Directory as a CSV and import them to Cloud Identity via the Admin Console.

（B）Use Google Cloud Directory Sync (GCDS) to synchronize users into Cloud Identity.

（C）Use the cloud Identity APIs and write a script to synchronize users to Cloud Identity.

（D）Ask each employee to create a Google account using self signup. Require that each employee use their company email address and password.

（A）Grant "project owner" role to crm-databases and roles/bigquery.dataViewer role to web-applications.

（B）Grant roles/bigquery.dataViewer role to crm-databases and appropriate roles to web-applications.

（C）Grant "project owner" role to crm-databases and the web-applications project.

（D）Grant "project owner" for web-applications appropriate roles to crm-databases.

（A）Deploy a private autopilot cluster

（B）Deploy a public autopilot cluster.

（C）Deploy a standard private cluster and enable shielded nodes.

（D）Deploy a standard public cluster and enable shielded nodes.

（A）Create a Compute Engine snapshot of your base VM. Create your instances from that snapshot.

（B）Create a Compute Engine snapshot of your base VM. Create your images from that snapshot.

（C）Create a custom Compute Engine image from a snapshot. Create your instances from that image.

（D）Create a custom Compute Engine image from a snapshot. Create your images from that image.

（A）Create two configurations using gcloud config. Write a script that sets configurations as active, individually. For each configuration, use gcloud compute instances list to get a list of compute resources.

（B）Go to Cloud Shell and export this information to Cloud Storage on a daily basis.

（C）Create two configurations using gsutil config. Write a script that sets configurations as active, individually. For each configuration, use gsutil compute instances list to get a list of compute resources.

（D）Go to GCP Console and export this information to Cloud SQL on a daily basis.

（A）Deploy a new version of your application in App Engine. Then go to App Engine settings in GCP Console and split traffic between the current version and newly deployed versions accordingly.

（B）Deploy a new version of your application in Google Kubernetes Engine instead of App Engine and then use GCP Console to split traffic.

（C）Deploy a new version as a separate app in App Engine. Then configure App Engine using GCP Console to split traffic between the two apps.

（D）Deploy a new version of your application in a Compute Engine instance instead of App Engine and then use GCP Console to split traffic.

（A）Create a Google spreadsheet with multiple Google Cloud resource combinations. On a separate sheet, import the current Google Cloud prices and use these prices for the calculations within formulas.

（B）Use the Google Cloud Pricing Calculator to determine the cost of every Google Cloud resource you expect to use. Use similar size instances for the web server, and use your current on-premises machines as a comparison for Cloud SQL.

（C）Use the Google Cloud Pricing Calculator and select the Cloud Operations template to define your web application with as much detail as possible.

（D）Implement a similar architecture on Google Cloud, and run a reasonable load test on a smaller scale.
Check the billing information, and calculate the estimated costs based on the real load your system usually handles.

（A）Navigate to Stackdriver Logging and select resource.labels.project_id="*"

（B）Create a Stackdriver Logging Export with a Sink destination to a BigQuery dataset. Configure the table expiration to 60 days.

（C）Create a Stackdriver Logging Export with a Sink destination to Cloud Storage. Create a lifecycle rule to delete objects after 60 days.

（D）Configure a Cloud Scheduler job to read from Stackdriver and store the logs in BigQuery. Configure the table expiration to 60 days.

（A）Use the M1 machine series on Compute Engine.

（B）Containerize the batch processing jobs and deploy them on Compute Engine.

（C）Use custom machine types on Compute Engine.

（D）Use Spot VMs on Compute Engine.

（A）Create a BigQuery table and load data in BigQuery. Run a SQL query on this table and drop this table after you complete your request.

（B）Load data in Cloud Datastore and run a SQL query against it.

（C）Create external tables in BigQuery that point to Cloud Storage buckets and run a SQL query on these external tables to complete your request.

（D）Create a Hadoop cluster and copy the AVRO file to NDFS by compressing it. Load the file in a hive table and provide access to your analysts so that they can run SQL queries.

（A）Set the CLOUDSDK_PROXY_USERNAME and CLOUDSDK_PROXY PASSWORD properties by using environment variables in your command line tool.

（B）Provide values for CLOUDSDK_USERNAME and CLOUDSDK_PASSWORD in the gcloud CLI tool configure file.

（C）Encode username and password in sha256 encoding, and save it to a text file. Use filename as a value in the gcloud configure set core/custom_ca_certs_file command.

（D）Configure username and password by using gcloud configure set proxy/username and gcloud configure set proxy/ proxy/password commands.

（A）Create an SSH keypair and store the public key as a project-wide SSH Key

（B）Configure Cloud Identity-Aware Proxy (or HTTPS resources

（C）Configure Cloud Identity-Aware Proxy for SSH and TCP resources.

（D）Create an SSH keypair and store the private key as a project-wide SSH Key

（A）Create a new Compute Engine instance and install Jenkins through the command line interface.

（B）Use GCP Marketplace to launch the Jenkins solution.

（C）Download and deploy the Jenkins Java WAR to App Engine Standard.

（D）Create a Kubernetes cluster on Compute Engine and create a deployment with the Jenkins Docker image.