Suggested answer

Named Credentials store the URL and authentication settings for an external endpoint, preventing credentials from being hardcoded in Apex. In Apex callouts, reference: req.setEndpoint('callout:MyNamedCredential/path'); Authentication protocols supported: Password (Basic Auth), OAuth 2.0 (client credentials, JWT bearer, web server flow), AWS Signature V4, JWT, No Auth. Per-User Named Credentials: Each Salesforce user authenticates individually to the external system. The named credential stores the URL; each user must complete an OAuth flow to store their own token. Ideal for user-context integrations. Per-Org: One shared credential for all users. Authentication secrets are stored securely in Salesforce infrastructure and never exposed to Apex code. Named Credentials automatically handle token refresh for OAuth.

Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.

Community comments (0)

No comments yet.

Sign in or create a free account to add a comment. Comments are moderated before they appear.

Plain text only, 3–2000 characters. A moderator reviews every comment before it is published.