117-304 · Question #104
Using Linux Virtual Server (LVS) provides which of the following features? (Select TWO correct answers)
The correct answer is A. Balancing load across real servers D. Checking and maintaining the integrity of services on real servers. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
Using Linux Virtual Server (LVS) provides which of the following features? (Select TWO correct answers)
Options
- ABalancing load across real servers
- BTaking over for fenced nodes
- CStopping services on other nodes when one node has a stopped service
- DChecking and maintaining the integrity of services on real servers
- EStarting and stopping virtual machines as needed
How the community answered
(27 responses)- A78% (21)
- B11% (3)
- C4% (1)
- E7% (2)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
6A and D are your answers. LVS is a load balancing solution, so A makes total sense, it distributes incoming traffic across real servers, and D covers the health-checking piece where LVS monitors those real servers to make sure their services are actually up and responding before sending traffic their way.
Saw this one and almost second-guessed myself on D because "integrity" sounds more like a filesystem or security tool than a load balancer, but that wording is just referring to LVS health checking, where it actively monitors real servers and pulls them out of rotation if they stop responding. A is the obvious one since load distribution is literally the whole point of LVS. B and C are there to trip you up if you confuse LVS with Pacemaker or corosync, which handle fencing and service failover logic between cluster nodes. E is just noise, that is VM orchestration territory, nothing to do with LVS. Stick with A and D.
I am going with A and C on this one, because LVS distributes traffic across real servers (that is the whole point of a virtual server setup), and I also remember reading that when a service goes down on one node the cluster has to stop that same service elsewhere to keep things consistent, which is exactly what C describes.
Nina, you have A right but C is off here, because when a service fails on one node the cluster actually starts it on another node to maintain availability, not stops it, which is what D captures.
Got A right away but D tripped me up the first few times because I kept thinking "integrity checking" sounded more like a storage or filesystem thing than something a load balancer does. LVS actually monitors the health of real servers and pulls them from rotation when they stop responding, which is what they mean by maintaining service integrity. Are you clear on how LVS health checking differs from what something like Pacemaker handles, or is that distinction still fuzzy?
Good point on the "integrity" wording being misleading, and I'd add that the mental shift that helped me was realizing LVS health checking is purely a traffic-routing decision at the load balancer layer, while Pacemaker is answering a totally different question one layer up, which is which node should own and restart a resource when the node itself goes down.