16 Salesforce Admin Interview Questions With Answers
Practise Salesforce admin scenarios covering permissions, record access, Flow, imports, reports and safe changes, with explanations and official references.
These 16 practice questions focus on decisions a Salesforce administrator must explain. They are not a prediction of an employer’s interview. Use a sandbox or training org for exercises, and describe the permissions, edition and automation already present before proposing a change.
Prepare a small demonstration
Build a fictional support queue, assign different access to an agent and a manager, then demonstrate a report and one tested record-triggered flow. Keep a short change log showing the requirement, implementation, expected result and rollback approach. Never use customer records or production credentials in an interview demonstration.
Interview questions & answers
Access
1.How would you give a new team access without copying an administrator profile?
List the tasks the team needs, identify object and field permissions, and grant the minimum appropriate access through permission sets or permission set groups. Then test with a representative user. A job title alone is not a permission specification; check whether export, deletion or sensitive fields are actually required.
2.A user can open an object but cannot see one record. What do you check?
First confirm the record exists and the user has object access. Then inspect organisation-wide defaults, ownership, role hierarchy, sharing rules and any explicit sharing that applies. Compare the affected user with a known working user. Do not widen the organisation-wide default just to fix one unexplained case.
3.How do field permissions differ from a page layout?
A page layout controls how fields and actions appear in that layout. Field-level security controls whether the user can access a field through supported interfaces. Hiding a salary field from one layout is not a security design. Verify field permissions and test other access paths such as reports and APIs.
4.When would you use a role rather than a permission set?
Use the role hierarchy when the requirement concerns access to records through organisational relationships. Use permissions when it concerns allowed actions on objects or fields. A manager may need wider record visibility but still should not receive permission to delete every record. Explain both requirements separately.
Automation
1.Would you build new automation with Workflow Rules or Process Builder?
I would evaluate Flow for a new declarative automation requirement. Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025. Existing automation may continue to run, but that is not a reason to extend a legacy design without review. Inventory existing behaviour and test a planned migration.
Salesforce: Workflow Rules and Process Builder support ended
2.When would you choose a before-save record-triggered flow?
For a suitable change to fields on the record being saved, I would consider a before-save flow. If the requirement needs related-record actions or a later action, I would evaluate the appropriate after-save or asynchronous design. I would check the available Flow capabilities in the org instead of choosing solely for convenience.
3.How would you investigate a flow that sends duplicate notifications?
Reproduce the issue with a test record and inspect entry criteria, changed-field conditions, active versions and other automation on the same event. Determine whether a later update retriggers the flow. Add a precise transition condition or another justified safeguard, then test creation, update, re-entry and bulk changes.
4.What should a flow error path do?
It should leave the user or operator with an actionable result while avoiding sensitive information in messages. For example, record a failed integration handoff for follow-up rather than displaying a credential or silently treating the action as complete. Test the fault path as deliberately as the successful path.
Data
1.How would you import accounts without creating duplicates?
Inspect the source data, define a reliable matching key and agree how existing accounts should be updated. Test a small sample in a safe environment, including duplicate and missing-key cases. Record the import mapping and reconciliation totals. A matching company name alone may merge unrelated organisations.
2.A CSV import partly fails. What do you do next?
Separate successful rows from failed rows and read the row-level errors. Fix the specific mapping, validation, access or data issue before retrying only the appropriate subset. Reconcile source counts and target records so a retry does not duplicate successful work. Keep the original file and outcome report for recovery.
3.When is a validation rule preferable to guidance text?
Use a validation rule when an agreed data condition must block a save, such as an invalid combination of status and required approval date. Use guidance when the user needs help making a judgement. Test the rule against integrations, imports, existing records and authorised exceptions before activation.
Reporting
1.Why might a manager’s report show fewer rows than expected?
Check the report type, filters, date range, record relationships and the viewer’s access. Compare a small known set of records against the report. Distinguish a reporting definition problem from a sharing problem. Broadening permissions without understanding the missing rows can expose unrelated data.
2.How do you define a trustworthy conversion dashboard?
Agree the numerator, denominator, reporting period and status definitions with the business. For example, specify whether conversion uses opportunities created this month or opportunities closed this month. Validate a sample manually and document excluded records. A polished chart cannot repair an ambiguous metric.
Delivery
1.What belongs in a change request before you configure Salesforce?
Capture the user task, acceptance criteria, affected records, access requirements, automation dependencies and expected volume. Include an owner for sign-off and a recovery approach. For a required field, ask how older records and integrations will supply it before changing the production configuration.
2.How would you release a new approval-related flow?
Test representative approved, rejected, missing-data and unauthorised scenarios in a safe environment. Review dependencies and coordinate the release with the process owner. Verify the active version and permissions after deployment, monitor failures, and retain a practical way to disable or replace the change if needed.
3.How do you respond when someone asks for administrator access to solve a problem?
Ask which task is blocked and reproduce the access failure. Grant the narrow permission or record access needed after review, then test the task again. If temporary elevated access is justified, agree its scope, owner and removal time. Do not make permanent administrator access the default support workaround.
Check your own material with the Free interview answer grader.
