Free PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Exam Braindumps (page: 23)

Page 22 of 46

Your organization wants to collect system logs that will be used to generate dashboards in Cloud Operations for their Google Cloud project. You need to configure all current and future Compute Engine instances to collect the system logs and you must ensure that the Ops Agent remains up to date.
What should you do?

  1. Use the gcloud CLI to install the Ops Agent on each VM listed in the Cloud Asset Inventory
  2. Select all VMs with an Agent status of Not detected on the Cloud Operations VMs dashboard Then select Install agents
  3. Use the gcloud CLI to create an Agent Policy.
  4. Install the Ops Agent on the Compute Engine image by using a startup script

Answer(s): C

Explanation:

The best option for configuring all current and future Compute Engine instances to collect system logs and ensure that the Ops Agent remains up to date is to use the gcloud CLI to create an Agent Policy. An Agent Policy is a resource that defines how Ops Agents are installed and configured on VM instances that match certain criteria, such as labels or zones. Ops Agents are software agents that collect metrics and logs from VM instances and send them to Cloud Operations products, such as Cloud Monitoring and Cloud Logging. By creating an Agent Policy, you can ensure that all current and future VM instances that match the policy criteria will have the Ops Agent installed and updated automatically. This way, you can collect system logs from all VM instances and use them to generate dashboards in Cloud Operations.



Your company has a Google Cloud resource hierarchy with folders for production test and development Your cyber security team needs to review your company's Google Cloud security posture to accelerate security issue identification and resolution You need to centralize the logs generated by Google Cloud services from all projects only inside your production folder to allow for alerting and near-real time analysis.
What should you do?

  1. Enable the Workflows API and route all the logs to Cloud Logging
  2. Create a central Cloud Monitoring workspace and attach all related projects
  3. Create an aggregated log sink associated with the production folder that uses a Pub Sub topic as the destination
  4. Create an aggregated log sink associated with the production folder that uses a Cloud Logging bucket as the destination

Answer(s): D

Explanation:

The best option for centralizing the logs generated by Google Cloud services from all projects only inside your production folder is to create an aggregated log sink associated with the production folder that uses a Cloud Logging bucket as the destination. An aggregated log sink is a log sink that collects logs from multiple sources, such as projects, folders, or organizations. A Cloud Logging bucket is a storage location for logs that can be used as a destination for log sinks. By creating an aggregated log sink with a Cloud Logging bucket, you can collect and store all the logs from the production folder in one place and allow for alerting and near-real time analysis using Cloud Monitoring and Cloud Operations.



You are configuring the frontend tier of an application deployed in Google Cloud The frontend tier is hosted in ngmx and deployed using a managed instance group with an Envoy-based external HTTP(S) load balancer in front The application is deployed entirely within the europe-west2 region: and only serves users based in the United Kingdom. You need to choose the most cost-effective network tier and load balancing configuration What should you use?

  1. Premium Tier with a global load balancer
  2. Premium Tier with a regional load balancer
  3. Standard Tier with a global load balancer
  4. Standard Tier with a regional load balancer

Answer(s): B

Explanation:

The most cost-effective network tier and load balancing configuration for your frontend tier is to use Premium Tier with a regional load balancer. Premium Tier is a network tier that provides high- performance and low-latency network connectivity across Google's global network. A regional load balancer is a load balancer that distributes traffic within a single region. Since your application is deployed entirely within the europe-west2 region and only serves users based in the United Kingdom, you can use Premium Tier with a regional load balancer to optimize the network performance and cost.



You recently deployed your application in Google Kubernetes Engine (GKE) and now need to release a new version of the application You need the ability to instantly roll back to the previous version of the application in case there are issues with the new version Which deployment model should you use?

  1. Perform a rolling deployment and test your new application after the deployment is complete
  2. Perform A. B testing, and test your application periodically after the deployment is complete
  3. Perform a canary deployment, and test your new application periodically after the new version is deployed
  4. Perform a blue/green deployment and test your new application after the deployment is complete

Answer(s): D

Explanation:

The best deployment model for releasing a new version of your application in GKE with the ability to instantly roll back to the previous version is to perform a blue/green deployment and test your new application after the deployment is complete. A blue/green deployment is a deployment strategy that involves creating two identical environments, one running the current version of the application (blue) and one running the new version of the application (green). The traffic is switched from blue to green after testing the new version, and if any issues are discovered, the traffic can be switched back to blue instantly. This way, you can minimize downtime and risk during deployment.






Post your Comments and Discuss Google PROFESSIONAL-CLOUD-DEVOPS-ENGINEER exam with other Community members:

Exam Discussions & Posts