Which NAC deployment installs the scanning engine on the domain controller instead of the end point device?

Which NAC deployment installs the scanning engine on the domain controller instead of the end point device?

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

Answer: (C)

In NAC, you can perform posture checks with or without a resident agent on endpoints. When the scanning engine and policy enforcement are centralized, you’re using agentless NAC rather than pushing agents to every device. The “volatile agent” flavor means a temporary agent can be deployed to a device for deeper checks if needed, then removed, while the persistent scanning remains on the central controller (often the domain controller). This combination fits the scenario where the scanning engine lives on the domain controller instead of on the end point, without forcing a permanent agent on every device. The other options imply endpoints hosting the scanning engine (persistent agent) or rely on local enforcement devices rather than a central scanner.

In NAC, you can perform posture checks with or without a resident agent on endpoints. When the scanning engine and policy enforcement are centralized, you’re using agentless NAC rather than pushing agents to every device. The “volatile agent” flavor means a temporary agent can be deployed to a device for deeper checks if needed, then removed, while the persistent scanning remains on the central controller (often the domain controller). This combination fits the scenario where the scanning engine lives on the domain controller instead of on the end point, without forcing a permanent agent on every device. The other options imply endpoints hosting the scanning engine (persistent agent) or rely on local enforcement devices rather than a central scanner.