Exam Associate Cloud Engineer topic 1 question 32 discussion

First of all D is incorrect, Groups are used to define alerts on set of resources(such as VM instances, databases, and load balancers). FYI tried adding Two projects into a group it did not allowed me as the "AND"/"OR" criteria for the group failed with this combination of resources. C is correct because, When you intially click on Monitoring(Stackdriver Monitoring) it creates a workspac(a stackdriver account) linked to the ACTIVE(CURRENT) Project from which it was clicked. Now if you change the project and again click onto Monitoring it would create an another workspace(a stackdriver account) linked to the changed ACTIVE(CURRENT) Project, we don't want this as this would not consolidate our result into a single dashboard(workspace/stackdriver account). If you have accidently created two diff workspaces merge them under Monitoring > Settings > Merge Workspaces > MERGE. If we have only one workspace and two projects we can simply add other GCP Project under Monitoring > Settings > GCP Projects > Add GCP Projects. In both of these cases we did not create a GROUP, we just linked GCP Project to the workspace(stackdriver account).

C is correct not D

The correct answer is **C. Configure a single Stackdriver account, and link all projects to the same account.** Stackdriver Monitoring (now Google Cloud Monitoring) doesn't work on a per-project account basis. There's a single Monitoring service that spans your entire Google Cloud organization. All projects within the organization can automatically report metrics to this single Monitoring instance. You don't need to create separate accounts or use complex workarounds like Shared VPC or inter-project service accounts. Option C directly addresses this by leveraging the inherent design of Cloud Monitoring. Options A, B, and D are incorrect because they introduce unnecessary complexity and don't utilize the built-in functionality of Google Cloud Monitoring for consolidated reporting across multiple projects. They might even lead to permission issues and difficulties in maintaining a unified view of your resources.

This method provides a centralized and flexible way to monitor resources across different projects, without requiring complex network configurations or additional accounts.

D is incorrect because a stackdriver group can group resources but not projects. Creating a single Stackdriver account in one project and creating a Group with other project names as criteria does not automatically aggregate and monitor metrics from different projects in a single dashboard. While creating a Group can help organize and manage metrics, it does not provide a solution for linking and monitoring metrics from different projects. You would still need to separately configure and link each project to the Stackdriver account to monitor their respective metrics.

C is more correct, just link them into one

Option C is the recommended approach because it allows you to configure a single Stackdriver account and link all your projects to this account. This way, you can centralise monitoring, create custom dashboards, set up alerts, and gain a unified view of your resources distributed across different projects in a more straightforward and consolidated manner. It provides a single point of access and management for monitoring across all projects, which is typically the desired outcome for multi-project environments.

C is more correct, just link them into one

https://cloud.google.com/monitoring/settings Best practices for scoping projects We recommend that you use a new Google Cloud project or one without resources as the scoping project when you want to view metrics for multiple Google Cloud projects or AWS accounts. When a metrics scope contains monitored projects, to chart or monitor only those metrics stored in the scoping project, you must specify filters that exclude metrics from the monitored projects. The requirement to use filters increases the complexity of chart and alerting policy, and it increases the possibility of a configuration error. The recommendation ensures that these scoping projects don't generate metrics, so there are no metrics in the projects to chart or monitor.

C is correct

C is correct because you can monitor multiple GCP projects from a single stackdriver account

c should be correct

Answer C. Configure a single Stackdriver account and link all projects to the same account. By linking all projects to the same Stackdriver account, you can consolidate monitoring and reporting for all resources across multiple projects. This can be done by following the instructions provided by Stackdriver on how to add projects to an account. Answer A is not the best solution since Shared VPC does not consolidate the monitoring and reporting of resources distributed over different projects. Answer B is not an efficient solution as it requires creating multiple Stackdriver accounts, which can lead to confusion and inefficiency. Answer D is not the best solution as it only groups the projects under one account, but it does not consolidate monitoring and reporting.

Have anybody all questions and want top share? Thanks!

If anyone is the contributor please share the dumps on [email protected]

C. Configure a single Stackdriver account, and link all projects to the same account.

Option C