Question 340
A proposed fix must be validated: A regulated organization uses an existing AD FS identity provider for federated Microsoft 365 sign-in and must troubleshoot a login loop. What should a controlled test show after implementation?
Explanation
Correct Answer
A test user obtains a valid token through the configured federated sign-in route. The case concerns federated authentication dependency: A regulated organization uses an existing AD FS identity provider for federated Microsoft 365 sign-in and must troubleshoot a login loop. Federation delegates authentication decisions through a trusted identity provider with its own operational dependencies. This answers the acceptance evidence for this change because it addresses the explicit constraint. The action being validated is: repair the failing AD FS trust or token-signing condition through controlled federation administration. The check must use the affected users, data, or devices.
Incorrect Answers
PTA is a cloud sign-in method with on-premises validation dependency, unlike PHS-only validation. The reason this does not settle the present case is the actual condition: Federated sign-in depends on trust, token issuance, and reachability of the configured identity provider.
PHS creates a cloud authentication path while preserving configured hybrid identity lifecycle. The current corrective requirement is: Repair the failing AD FS trust or token-signing condition through controlled federation administration.
Matching source and cloud objects is identity continuity work, not a bulk user recreation step. The appropriate acceptance check is: A test user obtains a valid token through the configured federated sign-in route.