Question 440
At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing EMS architecture, operating-system support and server management during a security policy acceptance test (FCT-7.4-1.2-110). The observed endpoint management issue is: A company moves EMS to a new host but retains DNS pointing to the former management address for remote agents. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to include DNS TTL and remote-device verification in every EMS migration plan. It mitigates the actual failure: A company moves EMS to a new host but retains DNS pointing to the former management address for remote agents. A suitable correction is to update supported EMS public or private DNS and client connectivity configuration during the migration cutover; its proof is that test roaming endpoints resolve and connect to the intended new management service without stale entries.
Incorrect Answers
“Check endpoint management-plane reachability and application data paths separately during onboarding” checks a different ongoing risk rather than the reported failure: a company moves EMS to a new host but retains DNS pointing to the former management address for remote agents. The relevant mechanism is agent-to-EMS management transport depends on correct service discovery after infrastructure changes. The directly matched preventive control is “Include DNS TTL and remote-device verification in every EMS migration plan”.
“Record license ownership and post-install setup steps in the EMS server commissioning record” checks a different ongoing risk rather than the reported failure: a company moves EMS to a new host but retains DNS pointing to the former management address for remote agents. The relevant mechanism is agent-to-EMS management transport depends on correct service discovery after infrastructure changes. The directly matched preventive control is “Include DNS TTL and remote-device verification in every EMS migration plan”.
“Monitor registration connectivity from representative endpoint network locations” checks a different ongoing risk rather than the reported failure: a company moves EMS to a new host but retains DNS pointing to the former management address for remote agents. The relevant mechanism is agent-to-EMS management transport depends on correct service discovery after infrastructure changes. The directly matched preventive control is “Include DNS TTL and remote-device verification in every EMS migration plan”.