The VP of Sales at Cloud Kicks is receiving an error message that prevents them form saving an Opportunity. The administrator attempted the same edit without receiving an error. How can the…

Question

Options

• AEdit the page layout.
• BView the setup audit trail.
• CLog in as the user
• DReview the sharing model

• A
  13% (8)
• B
  3% (2)
• C
  78% (47)
• D
  5% (3)

Explanation

Logging in as the user (C) lets the administrator reproduce the exact experience - same profile, permissions, and record access - making it the only way to see the precise error the VP is encountering rather than inferring it indirectly.

Why the distractors are wrong:

• A (Edit page layout): Page layouts control field arrangement and visibility, not save errors caused by permission or validation issues.
• B (View setup audit trail): The audit trail records configuration changes, not runtime errors experienced by end users.
• D (Review the sharing model): Sharing controls record access, not the specific save error; and the administrator already confirmed they could save without error, ruling out a simple sharing gap as the explanation.

Memory tip: Think "see what they see" - when a user reports an error you can't reproduce, the only true validation is stepping into their shoes via Login As User, which is exactly what Salesforce's feature is called under Setup > Users.

No community discussion yet for this question.