IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 24 of 30
A university is planning to set up an identity solution for its alumni. A third-party identity provider will be used for single sign-on Salesforce will be the system of records. Users are getting error messages when logging in. Which Salesforce feature should be used to debug the issue?
Full set: 248 questionsThe Login History page is the primary administrative tool in Salesforce for troubleshooting user login issues, including those related to Single Sign-On (SSO). It provides a detailed record of all login attempts, capturing the user, login time, source IP, and, most importantly, the login status. For failed attempts, it displays a specific reason, such as "Failed: SAML Assertion Invalid" or "Failed: User Not Found," which is essential for diagnosing the root cause of SSO errors. This makes it the most direct and efficient feature for debugging the problem described.
A. Apex Exception Email: This feature is for notifying administrators about unhandled exceptions in Apex code. A standard SSO login failure is a configuration or assertion issue, not typically an Apex code crash.
B. View Setup Audit Trail: This tool tracks administrative changes to the organization's configuration. It is useful for seeing if SSO settings were changed, but not for debugging a specific user's login attempt in real-time.
C. Debug Logs: These provide verbose transaction logs for debugging Apex code, Visualforce, and API calls. While potentially useful for complex Just-in-Time (JIT) provisioning issues, Login History is the more appropriate first step for any login failure.
1. Salesforce Help Documentation, "Monitor Login History": "As an administrator, you can monitor all login attempts for your organization... For example, the Status column shows whether the login succeeded. If the login failed, the column shows the reason for the failure, such as an incorrect password or a login lockout." This directly supports using Login History to find the reason for login failures.
2. Salesforce Help Documentation, "Troubleshoot SAML Single Sign-On Errors": This guide explicitly lists checking the login history as a key troubleshooting step. It states, "From Setup, in the Quick Find box, enter Login History, then select Login History... Review the login history for the user who can’t log in. Look for a Failed status and a specific reason." This confirms its role in debugging SSO.
3. Salesforce Identity and Access Management Architect Documentation, "Troubleshoot Single Sign-On (SSO) Issues": "The first place to check when a user can’t log in with SSO is the Login History page... The Status column tells you why the login failed." This reference from the relevant architect-level documentation designates Login History as the primary diagnostic tool.
Keep practicing
Take the free IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice questions
- Question 2Universal Containers (UC) is planning to deploy a custom mobile app that will allow users…
- Question 3Universal containers (UC) is setting up Delegated Authentication to allow employees to lo…
- Question 4Universal Containers (UC) wants to use Salesforce for sales orders and a legacy of system…
- Question 5Universal containers (UC) is successfully using Delegated Authentication for their salesf…
- Question 6Universal Containers (UC) plans to use a SAML-based third-party IdP serving both of the S…
- Question 7Universal Containers (UC) would like its community users to be able to register and log i…
