Free VMware 3V0-32.23 Actual Exam Questions - Question 7 Discussion
following:
Three data centers in three geographical locations.
Each site has 1,000 logging sources that send events to VMware Aria Operations for Logs.
The customer has the following requirements:
Minimize the resources footprint in the management cluster where VMware Aria Operations for Logs
will be deployed.
VMware Aria Operations for Logs must be highly available with no single points of failure.
Logs collected from any data center must be protected against site failure.
Which three design decisions would the architect choose to achieve the requirements? (Choose
three.)
C forwarding logs between data centers protects against site failure. D is needed to avoid loops from that forwarding. E centralizes logs to one site, minimizing resources and ensuring HA without multiple big clusters.
It’s C because forwarding logs between sites ensures no data loss if one site fails.
Makes sense to rule out A and B since they add a big resource footprint. I think E is key because forwarding all logs to one site centralizes management and helps with HA without extra clusters everywhere. Adding D also seems smart to avoid forwarding loops, which could cause issues if logs are sent between multiple sites. So I’d pick C for cross-site forwarding to protect against site failure, D for loop prevention, and E for centralized collection and minimizing resources. That combo seems to cover the HA and footprint requirements best.
Not B, since deploying nine medium nodes per site seems heavy and contradicts minimizing resource footprint. C looks better for protecting logs against site failure by forwarding them between sites.
E. Centralizing logs to one site minimizes resource use in the management cluster and helps meet HA and site failure protection requirements without complex multi-site replication.
A/E/F? A smaller number of larger nodes cuts resource use, sending all logs to one site (E) keeps things centralized, and forwarding critical logs (F) ensures key data is protected without overloading the system.
C imo, because forwarding logs between data centers ensures copies exist if one site fails, meeting the protection requirement. D also makes sense to avoid forwarding loops, which could happen with multiple clusters forwarding logs between each other. I’d skip E since sending all logs to a single data center might create a big resource hit there, contradicting the need to minimize footprint in the management cluster. So C and D together seem cleaner for high availability and no single points of failure without overloading one site. For the third choice, probably one that supports enough nodes
Maybe C, D, and E. Forwarding logs between sites and centralizing fits HA and footprint needs.
I’m thinking C, D, and F might work too. Forwarding logs between sites (C) protects against site failure, filters to avoid loops (D) are necessary, and sending only critical logs to a central cluster (F) could minimize resource use. Does that fit the HA and resource requirements?
Maybe C, D, and E. Forwarding logs between data centers (C) with filters to prevent loops (D) ensures no site failure causes data loss, and centralizing logs (E) keeps resources minimal in management clusters.
Makes sense to centralize logs for protection, so option E fits best.
It’s A, D, and E. Having four large nodes in one cluster per site covers HA, filters prevent loops, and forwarding all logs to one center centralizes data for protection. Seems to check all boxes here.