Question 880
A multi-site Fusion deployment fails to enroll its second array because identity-provider trust differs across Active Directory domains. First post-change operational check: The cause has been verified and the responsible change authority has approved corrective work. Which NEXT scoped response should the engineer choose?
Explanation
Correct Answer
This is the controlled correction: Implement vendor-supported multi-domain identity/fleet settings with scoped permissions. The targeted response addresses the confirmed cause and has a defined, limited change scope. In this implementation case, A multi-site Fusion deployment fails to enroll its second array because identity-provider trust differs across Active Directory domains.
Incorrect Answers
This alternative proposes: Repeat the initial finding without an authorized corrective step: Review LDAP trust, directory group mappings and cross-site fleet-role permissions. The fault has already been confirmed; repeating diagnosis without remediating it does not meet the task. In this implementation case, A multi-site Fusion deployment fails to enroll its second array because identity-provider trust differs across Active Directory domains.
This alternative proposes: Grant all directory users administrator rights to bypass cross-domain role checks. This step would bypass the condition the approved remediation must protect. In this implementation case, A multi-site Fusion deployment fails to enroll its second array because identity-provider trust differs across Active Directory domains.
This alternative proposes: Add extra storage capacity without addressing identity-provider and fleet authorization errors. The nearby check or task does not directly correct the verified cause. In this implementation case, A multi-site Fusion deployment fails to enroll its second array because identity-provider trust differs across Active Directory domains.