Which NAC deployment installs the scanning engine on the domain controller rather than the endpoint it protects?

Which NAC deployment installs the scanning engine on the domain controller rather than the endpoint it protects?

• A. Agentless NAC
• B. Persistent NAC
• C. Agentless NAC Volatile Agent
• D. Local NAC

Answer: (C)

This question tests how a NAC deployment places its scanning engine. In an agentless volatile agent setup, the scanning engine runs on a central server—typically a domain controller—and uses a temporary, non-persistent agent to perform checks on endpoints as they connect. The endpoint itself does not host a permanent agent, which matches the idea of installing the engine on the domain controller rather than on the protected device. This approach provides centralized visibility and control without leaving persistent software on each endpoint. Other options describe different models: a non-volatile agentless approach doesn’t specify central engine placement, persistent NAC uses long‑lived agents on endpoints, and local NAC enforces at the endpoint itself.

This question tests how a NAC deployment places its scanning engine. In an agentless volatile agent setup, the scanning engine runs on a central server—typically a domain controller—and uses a temporary, non-persistent agent to perform checks on endpoints as they connect. The endpoint itself does not host a permanent agent, which matches the idea of installing the engine on the domain controller rather than on the protected device. This approach provides centralized visibility and control without leaving persistent software on each endpoint.

Other options describe different models: a non-volatile agentless approach doesn’t specify central engine placement, persistent NAC uses long‑lived agents on endpoints, and local NAC enforces at the endpoint itself.