2V0-32.24 Question 62
Single answerYou are tasked with designing a vRealize Log Insight deployment for an organization that generates approximately 15,000 events per second (EPS) across its infrastructure. The organization requires a solution that can handle this load with sufficient redundancy and ensure logs are retained for 30 days. Based on VMware's best practices, how should you size the deployment?
- A
Deploy a single-node cluster with sufficient storage configured for 30 days of retention.
- B
Deploy a 3-node cluster with each node configured to handle the required EPS and storage for 30 days.
- C
Deploy a 6-node cluster, with each node distributing the EPS load and configured for 30 days of storage retention.
- D
Deploy a 2-node cluster with each node configured for 15,000 EPS and storage for 30 days.
Show answer and explanation
Correct answer: C
Explanation
To size a vRealize Log Insight deployment for 15,000 EPS with 30 days of log retention, it is important to ensure the deployment can handle the incoming log volume, provide redundancy for high availability, and meet storage requirements. A 6-node cluster is best suited for this scenario, as it distributes the load evenly, ensures fault tolerance, and meets VMware’s recommended best practices for high EPS environments.
- A. Incorrect.
A single-node cluster is not recommended for production environments requiring high availability and redundancy. A single node cannot handle 15,000 EPS reliably over time and does not provide fault tolerance.
- B. Incorrect.
A 3-node cluster is generally suitable for smaller workloads. For 15,000 EPS, it may not provide adequate performance or redundancy based on VMware's sizing guidelines.
- C. Correct.
A 6-node cluster is appropriate for high EPS workloads like 15,000 EPS. This configuration ensures the load is distributed evenly among nodes, provides redundancy, and meets storage retention requirements for 30 days.
- D. Incorrect.
A 2-node cluster is not a supported architecture for vRealize Log Insight. VMware recommends starting with at least 3 nodes for production-grade deployments.