Google ASSOCIATE-CLOUD-ENGINEER Online Practice Questions and Exam Preparation

Google ASSOCIATE-CLOUD-ENGINEER Online Questions & Answers

• Question 181:

  Your company uses Cloud Storage to store application backup files for disaster recovery purposes. You want to follow Google's recommended practices. Which storage option should you use?

  A. Multi-Regional Storage
  B. Regional Storage
  C. Nearline Storage
  D. Coldline Storage
  D. Coldline Storage

  ---

  Explanation

  https://cloud.google.com/storage/docs/storage-classes#nearline

  Coldline is a Cloud Storage class designed for long-term archival and disaster recovery. Coldline is perfect for the archival needs of big data or multimedia content, allowing businesses to archive years of data. Coldline provides fast and instant (millisecond) access to data and changes the way that companies think about storing and accessing their cold data.

  Google Cloud Storage Multi-Regional is a highly available and geo-redundant storage class. It's the best storage class for business continuity, or for serving multimedia content to geographically distributed users.

  Google Cloud Storage Regional is a highly available storage class redundant within a single region. It's ideal for pairing storage and compute resources within a region, to deliver low end-to-end latency and high throughput for workloads such as data transcoding or big data analytics workloads

• Question 182:

  Your organization has strict requirements to control access to Google Cloud projects. You need to enable your Site Reliability Engineers (SREs) to approve requests from the Google Cloud support team when an SRE opens a support case. You want to follow Google-recommended practices. What should you do?

  A. Add your SREs to roles/iam.roleAdmin role.
  B. Add your SREs to roles/accessapproval approver role.
  C. Add your SREs to a group and then add this group to roles/iam roleAdmin role.
  D. Add your SREs to a group and then add this group to roles/accessapproval approver role.
  D. Add your SREs to a group and then add this group to roles/accessapproval approver role.

  ---

  Explanation

  Add your SREs to a group and then add this group to roles/accessapproval approver role. -Google recommendation.

• Question 183:

  You've been running App Engine applications in a Standard Environment for a few weeks. With several successful deployments, you've just deployed a broken version, and the developers have gone home for the day. What is the fastest way to get the site back into a functioning state?

  A. Have the developers fix the issue and deploy.
  B. Use the gcloud app rollback command.
  C. In the UI, click Traffic Splitting and direct 100% of the traffic to the previous version.
  D. In the UI, click the Rollback button on the versions page.
  C. In the UI, click Traffic Splitting and direct 100% of the traffic to the previous version.

  ---

  Explanation

• Question 184:

  You created a Kubernetes deployment by running kubectl run nginx image=nginx replicas=1. After a few days, you decided you no longer want this deployment. You identified the pod and deleted it by running kubectl delete pod. You noticed the pod got recreated.

  $ kubectl get pods NAME READY STATUS RESTARTS AGE nginx-84748895c4-nqqmt 1/1 Running 0 9m41s $ kubectl delete pod nginx-84748895c4-nqqmt pod nginx-84748895c4-nqqmt deleted $ kubectl get pods NAME READY STATUS RESTARTS AGE nginx-84748895c4-k6bzl 1/1 Running 0 25s

  What should you do to delete the deployment and avoid pod getting recreated?

  A. kubectl delete deployment nginx
  B. kubectl delete-deployment=nginx
  C. kubectl delete pod nginx-84748895c4-k6bzl-no-restart 2
  D. kubectl delete inginx
  A. kubectl delete deployment nginx

  ---

  Explanation

  This command correctly deletes the deployment. Pods are managed by kubernetes workloads (deployments). When a pod is deleted, the deployment detects the pod is unavailable and brings up another pod to maintain the replica count. The only way to delete the workload is by deleting the deployment itself using the kubectl delete deployment command. $ kubectl delete deployment nginx deployment.apps nginx deleted Ref: https://kubernetes.io/docs/reference/kubectl/cheatsheet/#deleting-resources

• Question 185:

  You created a Kubernetes deployment by running kubectl run nginx image=nginx labels=app=prod. Your Kubernetes cluster is also used by a number of other deployments. How can you find the identifier of the pods for this nginx deployment?

  A. kubectl get deployments utput=pods
  B. gcloud get pods elector="app=prod"
  C. kubectl get pods -I "app=prod"
  D. gcloud list gke-deployments -filter={pod }
  C. kubectl get pods -I "app=prod"

  ---

  Explanation

  This command correctly lists pods that have the label app=prod. When creating the deployment, we used the label app=prod so listing pods that have this label retrieve the pods belonging to nginx deployments. You can list pods by using Kubernetes CLI kubectl get pods.

  Ref: https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container- images/ Ref: https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container- images/#list- containers-filtering-by-pod-label

• Question 186:

  You need to migrate invoice documents stored on-premises to Cloud Storage. The documents have the following storage requirements:

  Documents must be kept for five years.

  Up to five revisions of the same invoice document must be stored, to allow for corrections. Documents older than 365 days should be moved to lower cost storage tiers.

  You want to follow Google-recommended practices to minimize your operational and development costs.

  What should you do?

  A. Enable retention policies on the bucket, and use Cloud Scheduler to invoke a Cloud Function to move or delete your documents based on their metadata.
  B. Enable retention policies on the bucket, use lifecycle rules to change the storage classes of the objects, set the number of versions, and delete old files.
  C. Enable object versioning on the bucket, and use Cloud Scheduler to invoke a Cloud Functions instance to move or delete your documents based on their metadata.
  D. Enable object versioning on the bucket, use lifecycle conditions to change the storage class of the objects, set the number of versions, and delete old files.
  B. Enable retention policies on the bucket, use lifecycle rules to change the storage classes of the objects, set the number of versions, and delete old files.

  ---

  Explanation

• Question 187:

  You recently discovered that your developers are using many service account keys during their development process. While you work on a long term improvement, you need to quickly implement a process to enforce short-lived service account credentials in your company. You have the following requirements:

  1.All service accounts that require a key should be created in a centralized project called pj-sa.

  2.Service account keys should only be valid for one day.

  You need a Google-recommended solution that minimizes cost. What should you do?

  A. Implement a Cloud Run job to rotate all service account keys periodically in pj-sa. Enforce an org policy to deny service account key creation with an exception to pj-sa.
  B. Implement a Kubernetes CronJob to rotate all service account keys periodically. Disable attachment of service accounts to resources in all projects with an exception to pj-sa.
  C. Enforce an org policy constraint allowing the lifetime of service account keys to be 24 hours. Enforce an org policy constraint denying service account key creation with an exception on pj-sa.
  D. Enforce a DENY org policy constraint over the lifetime of service account keys for 24 hours. Disable attachment of service accounts to resources in all projects with an exception to pj-sa.
  C. Enforce an org policy constraint allowing the lifetime of service account keys to be 24 hours. Enforce an org policy constraint denying service account key creation with an exception on pj-sa.

  ---

  Explanation

  You can use an org policy to enforce a 24-hour lifetime for service account keys.

  You can use an org policy to deny service account key creation, with an exception for the pj-sa project.

  This is a Google-recommended solution and it is relatively inexpensive.

• Question 188:

  Which of the following is a valid use case for using a primitive role?

  A. When granting permission to a development project or to the development team.
  B. When there are more than 10 users.
  C. When creating a custom role requires more than 10 permissions.
  D. When granting permission to a production project, or to a third-party company.
  A. When granting permission to a development project or to the development team.

  ---

  Explanation

• Question 189:

  You're attempting to deploy a new instance that uses the centos 7 family. You can't recall the exact name of the family. Which command could you use to determine the family names?

  A. gcloud compute instances list
  B. gcloud compute images show-families
  C. gcloud compute instances show-families
  D. gcloud compute images list
  D. gcloud compute images list

  ---

  Explanation

• Question 190:

  Your company wants to migrate their on-premises workloads to Google Cloud. The current on-premises workloads consist of:

  1.A Flask web application

  2.A backend API

  3.A scheduled long-running background job for ETL and reporting

  You need to keep operational costs low. You want to follow Google-recommended practices to migrate these workloads to serverless solutions on Google Cloud. What should you do?

  A. Migrate the web application to App Engine and the backend API to Cloud Run. Use Cloud Tasks to run your background job on Compute Engine.
  B. Migrate the web application to App Engine and the backend API to Cloud Run. Use Cloud Tasks to run your background job on Cloud Run.
  C. Run the web application on a Cloud Storage bucket and the backend API on Cloud Run. Use Cloud Tasks to run your background job on Cloud Run.
  D. Run the web application on a Cloud Storage bucket and the backend API on Cloud Run. Use Cloud Tasks to run your background job on Compute Engine.
  B. Migrate the web application to App Engine and the backend API to Cloud Run. Use Cloud Tasks to run your background job on Cloud Run.

  ---

  Explanation

  https://cloud.google.com/architecture/migration-to-gcp-deploying-your-workloads