Question 500
An administrator is assessing this problem: A security operator sees risky logins that list older client application types while normal browser sign-ins are healthy. Where should an administrator look first to validate the suspected mechanism?
Explanation
Correct Answer
Filter sign-in records by client app, user, IP and error status. The case concerns identify legacy client in sign-in logs: A security operator sees risky logins that list older client application types while normal browser sign-ins are healthy. Authentication diagnostics should evaluate the actual protocol and sign-in flow used. This answers the evidence needed to discriminate between possible causes because it addresses the explicit constraint. That evidence tests the underlying interpretation: client application type in Entra sign-in logs helps distinguish legacy protocol usage from modern interactive methods. It is more discriminating than unrelated service indicators.
Incorrect Answers
Smart lockout protects against brute-force attempts but can require operator troubleshooting. The reason this does not settle the present case is the actual condition: Client application type in Entra sign-in logs helps distinguish legacy protocol usage from modern interactive methods.
Modern authentication controls are only effective when unsupported legacy sign-in paths are closed. The records needed for this specific case concern: Filter sign-in records by client app, user, IP and error status.
Passwordless sign-in is a specific authentication method, not merely an MFA policy label. The current corrective requirement is: Investigate affected legacy clients and migrate or disable unsupported sign-in protocol use.