Question 1
At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing EMS architecture, operating-system support and server management during a Security Fabric integration test (FCT-7.4-1.2-001). The observed endpoint management issue is: A team moves from old Windows EMS to 7.4 Linux using only file copies and assumes a service-start proves successful data migration. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to stage migration rehearsals with policy counts and agent connectivity proof. It mitigates the actual failure: A team moves from old Windows EMS to 7.4 Linux using only file copies and assumes a service-start proves successful data migration. A suitable correction is to execute the supported EMS 7.4 data migration workflow and validate policies, registrations and credentials after import; its proof is that managed groups, intended configurations and a test endpoint registration survive the controlled migration.
Incorrect Answers
“Include disconnected-client behavior and eventual policy reconciliation in acceptance testing” checks a different ongoing risk rather than the reported failure: a team moves from old Windows EMS to 7.4 Linux using only file copies and assumes a service-start proves successful data migration. The relevant mechanism is eMS migration requires version-aware transfer and validation rather than copying application directories blindly. The directly matched preventive control is “Stage migration rehearsals with policy counts and agent connectivity proof”.
“Validate deployment package registration targets before promoting laboratory changes” checks a different ongoing risk rather than the reported failure: a team moves from old Windows EMS to 7.4 Linux using only file copies and assumes a service-start proves successful data migration. The relevant mechanism is eMS migration requires version-aware transfer and validation rather than copying application directories blindly. The directly matched preventive control is “Stage migration rehearsals with policy counts and agent connectivity proof”.
“Check expiry and hostname compatibility of management certificates before renewals” checks a different ongoing risk rather than the reported failure: a team moves from old Windows EMS to 7.4 Linux using only file copies and assumes a service-start proves successful data migration. The relevant mechanism is eMS migration requires version-aware transfer and validation rather than copying application directories blindly. The directly matched preventive control is “Stage migration rehearsals with policy counts and agent connectivity proof”.