A county partner endpoint-protection service deployment shows Down even though the service VMs exist. The protected workloads are powered off and have no Guest Introspection policy. What does healthy GI require?
Select an answer to reveal the explanation.
Short Explanation
GI health is a three-legged stool: guests must be on, Tools must have the introspection bits, and a policy has to send work to the partner service. A dark VM cannot check in.
Full Explanation
Healthy Guest Introspection for a county partner endpoint-protection service needs powered-on guests with Guest Introspection drivers installed and a GI or endpoint-protection policy assigned. Service VMs alone are not enough when protected workloads are powered off and have no GI policy.
Only the partner Service VM powered on—with guest power state and drivers optional—leaves GI unhealthy. A Carbon Black sensor group in Ready state does not replace GI health. Distributed firewall default-allow does not make GI healthy independent of guests and policy.
Exam caveat: GI health is guests on + drivers + policy (+ partner service)—all legs required.
Operational check: power on pilot workloads, confirm Tools GI drivers, assign GI/EPP policy, verify partner service health Up, and keep powered-off templates out of health expectations.
GI health needs live guests, drivers, and policy—not just a glowing partner SVM. Include powered-on pilot VMs in health dashboards, and stop declaring county partner EPP “up” when only the service tier is green. Keep powered-on guest, driver, and policy evidence beside partner SVM health with the EPP change record so the next on-call engineer cannot declare GI healthy from the service tier alone under pressure.