Salesforce Admin Interview Questions and Answers to help you find your next Salesforce Admin job.
Salesforce Admin Salary
The table below lists Average Annual Salesforce Admin Salary in Australia, Canada, India, United Kingdom and United States.
|Country||Average Annual Salary|
Q1. What is a Profile in Salesforce?
Profiles determine what users can do in Salesforce. They come with a set of permissions which grant access to particular objects, fields, tabs, and records. Each user can have only one profile.
Q2. What is a Role in Salesforce?
Roles determine what users can see in Salesforce based on where they are located in the role hierarchy. Users at the top of the hierarchy can see all the data owned by users below them. Users at lower levels can’t see data owned by users above them, or in other branches, unless sharing rules grant them access. Roles are optional but each user can have only one.
Q3. Explain Organization-wide defaults.
Organization-wide defaults (OWD) specify the default level of access users have to each others records. You use organization–wide sharing settings to lock down your data to the most restrictive level, and then use the other sharing tools to selectively give access to other users. For example, you can give all employees access to an object called Candidate to allow anyone to add a candidate to the database. But you can restrict access to Positions so that anyone can see the jobs available but only the employees with the proper permissions can edit them. OWD can be Private, Public Read Only, Public Read/Write or Controlled by Parent.
Q4. What is Role Hierarchy?
Role Hierarchy open up access to those higher in the hierarchy so they inherit access to all records owned by users below them in the hierarchy. Each role in the hierarchy represents a level of data access that a user or group of users needs. For example, you can restrict access to Candidates by setting the organization–wide default to Private, but allow recruiters to view and edit the candidate records that they own.
Q5. What are Sharing Rules?
Sharing Rules enable you to make automatic exceptions to organization–wide defaults for particular groups of users, to give them access to records they don’t own or can’t normally see. Sharing rules, like role hierarchies, are only used to give more users access to records—they can’t be stricter than your organization–wide default settings.
Q6. What is Manual Sharing?
Manual Sharing allows owners of particular records to share them with other users.
Q7. What is the use of Grant Access Using Hierarchies checkbox for a custom object?
Grant Access Using Hierarchies checkbox for a custom object is use to grant access to record to users who are above the record owner in role hierarchy. Unchecking the checkbox will make sure that users that are higher in the role hierarchy don’t receive automatic access.
Q8. What is Salesforce Identity?
Salesforce Identity is an identity and access management (IAM) service the lets you give the right people the right access to the right resources at the right time. You control who can access your orgs and who can use apps running on the Salesforce Platform, on-premises, in other clouds, and on mobile devices.
Q9. What is Single Sign-On?
Single sign-on (SSO) lets users access all authorized resources without logging in separately to each one—and without having to create (and remember) different user credentials for each app.
Q10. What is Social Sign-On?
Social sign-on allows users to log in to a Salesforce org with their username and password from an external authentication provider like Facebook, Twitter, LinkedIn, or Google.
Salesforce Admin Interview Questions
Q11. What are Governor Limits in Salesforce?
Because Apex runs in a multitenant environment, the Apex runtime engine strictly enforces limits so that runaway Apex code or processes don’t monopolize shared resources. If some Apex code exceeds a limit, the associated governor issues a runtime exception that can’t be handled.
You can specify users to receive an email notification when they invoke Apex code that surpasses 50% of allocated governor limits. Only per-request limits are checked for sending email warnings; per-org limits like concurrent long-running requests are not checked. These email notifications do not count against the daily single email limit.
Some of the Key Governor limits are:
|Governor Limit Description||Synchronous Limit||Asynchronous Limit|
|Total number of SOQL queries||100||200|
|Total number of records retrieved by SOQL queries||50,000|
|Total number of SOSL queries||2,000|
|Total number of DML statements||150|
|Total number of callouts (HTTP requests or web services calls)||100|
|Maximum CPU time on the Salesforce servers||10 seconds||60 seconds|
|Maximum execution time for each Apex transaction||10 minutes|
Please find complete list of Apex Governor limits here!
Q12. What is Salesforce Login Flow?
A login flow is used to direct users through a custom login process before they can access Salesforce org or Experience Cloud site. Login flow can be used to control the business processes to be followed when users log in to Salesforce. After Salesforce authenticates a user, the login flow directs the user through a process, such as enforcing strong authentication or collecting user information. When users complete the login flow successfully, they’re redirected to their Salesforce org or site. If unsuccessful, the flow can log out users immediately. Custom Login Flows can be created using Flow Builder or Visualforce.
Q13. What is Salesforce Flow?
Flow is an automation tool to collect data and performs actions in your Salesforce org or an external system. You can create Flows using Flow Builder. Salesforce Flow provides two types of flows:
- Screen Flows – guide users through a business process, capture users input
- Autolaunched Flows – launches when a record changes or user clicks a button
- Record-Triggered Flow – launches when a record is created, updated or deleted
- Schedule-Triggered Flow – launches at a specified time and frequency for each record in a batch
- Platform Event -Triggered Flow – launches when a platform message is received
- Autolaunched Flow (No Trigger) – launches when invoked by Apex, processes, REST API and more
Q14. List the Flow Types supported in Flow Builder.
Flow Builder supports below flow types:
- Screen Flow
- Autolaunched Flow with No Flow Trigger
- Autolaunched Flow with a Schedule Trigger
- Autolaunched Flow with a Record Trigger
- User Provisioning Flow
- Field Service Mobile Flow
- Field Service Embedded Flow
- Contact Request Flow
- Checkout Flow
- Orchestrator (Beta)
Q15. List various Flow Distribution Methods.
Flows can be distributed (made available to users) via:
- Flow actions
- Lightning pages
- Experience Builder pages
- Custom Aura components
- Custom Lightning web components
- Custom buttons or custom links
- Flow Orchestrator (Beta)
- Web tabs
- Direct flow URLs
- Visualforce pages
- Lightning Out
- Embedded Service deployments
Q16. What Is Einstein Discovery?
Salesforce Einstein Discovery augments your business intelligence with statistical modeling and supervised machine learning in a no-code-required, rapid-iteration environment. Einstein Discovery enables you to:
- Identify, surface, and visualize insights into your business data.
- Predict future outcomes and suggest ways to improve predicted outcomes in your workflows.
Q17. What are Salesforce Functions?
You can user Salesforce Functions can to build and integrate individual blocks of logic which extend your apps using the languages and tools of your choice. You write code that performs a specific task on trusted, managed Salesforce infrastructure, preauthenticated and preconfigured to use Salesforce data. Apex code, or a low-code solution such as a Salesforce Flow, then invokes your code on demand. Your function automatically scales to meet the load. Since Salesforce Functions is built and managed by Salesforce, this frees your app design from the API limits encountered by off-platform solutions.
You can use Salesforce functions to perform compute-heavy tasks that were previously challenging to do in your org. Salesforce Functions use cases include:
- Complex business calculations, such as loan processing, managing product license keys, contract billing, and demand forecasting
- Batch processing, such as daily inventory stocking, consumer goods assortments, ERP calculations, and material resource planning
- Resource-intensive back-office automation, such as document generation, mail merges, invoice creation, payroll processing, QR codes, and case routing
Q18. Describe the Guidance Center in Salesforce.
The Guidance Center is a resource library right inside of Salesforce. It offers personalized setup and learning resources that align with your experience level and business goals. Whether you’re an admin starting your first or your latest org implementation, you’ll find all sorts of guidance tailored to you and your business needs.
Each set of Guidance Center resources includes suggested videos, Trailhead modules, Help topics, PDFs, and in-app guidance to provide helpful how-tos.
Q19. What Is Incident Management?
Incident Management is an Out of the Box Service Cloud solution that helps your teams track large-scale disruptions and delegate tasks to the right experts to ensure your business delivers on customer expectations. With built-in fields, page layouts, and best practices.
Incident Management helps your service teams respond to any disruption and keep customers informed and with release management features, your team can implement changes to prevent the problems from happening again.
Incident Management can be accesses via Setup > Feature Settings > Service > Incident Management
Q20. Explain Field History Tracking.
You can select certain fields to track and display the field history in the History related list of an object. Field history data will be retained for up to 18 months through your org, and up to 24 months via the API. Field history tracking data doesn’t count against your Salesforce org’s data storage limits.
You can enable field history tracking for standard/custom objects in the object’s management settings. Changes to fields with more than 255 characters will only be tracked as edited, and their old and new values aren’t recorded.
Field Audit Trail lets you define a policy to retain archive field history data up to 10 years from the time the data was archived. This feature helps you comply with industry regulations related to audit capability and data retention. Field history is copied from the History related list into the
FieldHistoryArchive big object. You define one
HistoryRetentionPolicy for your related history lists, such as Account History, to specify Field Audit Trail retention policies for the objects you want to archive.
With Field Audit Trail, you can track up to 60 fields per object (can be increased to 100 at an additional cost). Without it, you can track only 20 fields per object. With Field Audit Trail, you retain archived field history data up to 10 years from the time the data was archived. Without it, you retain archived data for only 18 months.
Salesforce Admin Interview Questions
Q21. What are Quick Actions in Salesforce?
Quick Actions are used to create new records, invoke Lightning components, flows or Visualforce pages. Quick Actions are of two Types:
- Object Specific Actions – have automatic relationships to other records. You can use Object Specific Actions to quickly create or update records, log calls, send emails, and more in the context of a particular object.
- Global Actions – are not specific to any object and are not related to any object. They can be put anywhere actions are supported. You can use Global Actions to log call details, create or update records, or send email with without context of a particular object.
Q22. What are Session-Based Permission Sets?
A session-based permission set applies to a specific user session to grant someone functional access to permissions. With session-based permission sets, you can limit functional access for select permissions in a permission set to an activated session. When a session ends for any reason, a session-based permission set must be activated again before the user can access restricted resources. To make a Permission Set session-based you must select Session Activation Required when you create your permission set.
Q23. What is Enterprise Territory Management?
Enterprise Territory Management is used to manage and maintain a company’s sales territories. Enterprise Territory Management uses territory types, territory models, and territory model states. Territories help companies keep track of which reps are assigned to which accounts and opportunities. Some of the key elements of Territory Management are:
- Territory Type – help you organize your territories by key characteristics important to your company. Every territory you create has a territory type
- Territory – organize groups of accounts and the Salesforce users who work with those accounts. Territories are created based on territory types
- Territory Type Priority – helps you choose the appropriate territory type for territories
- Territory Model – represents a complete territory management system for your company. Modeling lets you create and preview multiple territory structures and different account and user assignments before you activate the model that works best
- Territory Hierarchy – shows a model’s territory structure and serves as its main interaction point
- Territory Model State – indicates whether a territory is in the planning stage, in active use, or archived
Q24. What Is Event Monitoring?
Event Monitoring lets you see the granular details of user activity in your organization. These user activities are refers as Events. You can view information about individual events or track trends in events to identify abnormal behavior and safeguard your company’s data. Some of the events that can be tracked by Event Monitoring are:
- URI (web clicks in Salesforce Classic)
- Lightning (web clicks, performance, and errors in Lightning Experience and the Salesforce mobile app)
- Visualforce page loads
- Application programming interface (API) calls
- Apex executions
- Report exports
Q25. Explain Delegated Administration in Salesforce.
Delegated administration can be used to assign limited admin privileges to users in your org who aren’t administrators. Some of the duties a Delegated administrators can perform are:
- Create and edit users in specified roles and all subordinate roles.
- Reset Passwords.
- Unlock users.
- Assign users to specified profiles.
- Assign or remove permission sets for users in their delegated groups.
- Create public groups and manage membership in specified public groups.
- Log in as a user who has granted login access to the administrator.
- Manage custom objects and customize nearly every aspect of a custom object.
This article will be updated soon, please come back for more Salesforce Admin Interview Questions!
Additional Salesforce Interview Questions
- Salesforce Integration Interview Questions
- Salesforce CPQ Interview Questions
- Saleforce Marketing Cloud Interview Questions
- Salesforce Vlocity Interview Questions
- Salesforce Field Service Interview Questions
The Thumbnail Story
The thumbnail picture used in this article was captured by me at Jenny Lake, Grand Teton National Park, Wyoming. Jenny Lake is located in Grand Teton National Park in the U.S. state of Wyoming. The lake was formed approximately 12,000 years ago by glaciers pushing rock debris which carved Cascade Canyon during the last glacial maximum, forming a terminal moraine which now impounds the lake.