Free VMware 3V0-32.23 Actual Exam Questions - Question 13 Discussion
The customer has the following requirements:
VMware Aria Operations for Logs cluster responds to multiple Virtual IP Addresses (VIPs)
Each event message received from a VIP is associated with a tag
Which two design decisions would the architect make to achieve the requirements? (Choose two.)
A/E? I think having interfaces on the same subnet as VIPs (E) is necessary for proper network routing, and dynamic tags (A) would let you tag events flexibly per VIP. Static tags might be too rigid here.
A/D? Dynamic tags cover changing VIPs and static tags lock in consistent labels, both needed for tagging per VIP. The subnet stuff feels less relevant since the main point is tagging events from VIPs.
It’s A and E for me. Using dynamic tags (A) makes sense because you can tag events based on which VIP they came from without needing to manually update tags if VIPs change. Plus, having nodes on the same subnet as VIPs (E) is the simplest way to avoid complex routing or firewall rules, keeping things straightforward and reliable. B sounds like overcomplicating the network setup when same-subnet is usually fine for VIPs and nodes.
A/D? Dynamic tags for flexibility, static tags for guaranteed VIP association.
A/D? Static tags guarantee consistent tagging, but dynamic tags let you flex based on VIPs. Having nodes on the same subnet as VIPs (E) seems simpler and avoids routing headaches compared to B.
D/E seems more practical; static tags are reliable, and VIPs usually share subnet with nodes.
D/B? Static tags ensure consistent labeling per VIP, and having nodes on different subnets than VIPs is common for better traffic control. Same subnet (E) could cause IP conflicts or routing issues in some setups.
D/B? Static tags make more sense to reliably mark events per VIP, and having nodes on different subnets from VIPs can help with network segregation and routing. Dynamic tags (A) feel less straightforward here.
It’s A and E. Dynamic tags let you assign different tags per VIP on the load balancer, and nodes having interfaces on the same subnet as VIPs helps with proper traffic routing and tagging.
Probably D and E, static tags keep it simple and VIPs usually share subnet.
D imo, static tags fit the requirement better for consistent tagging per VIP. Also, E makes more sense than B because VIPs usually live on the same subnet as the node interfaces to handle traffic correctly.
It’s D for sure since static tags make sense for consistent tagging from each VIP. Also think B is needed because different subnets help separate the VIP traffic properly in the cluster.
Maybe A and D