Salesforce Admin Exam Flashcards

Q: How many questions are on the Salesforce Admin exam?

The Salesforce Certified Administrator exam has 60 multiple-choice or multiple-select questions with a 105-minute time limit. The local exam guide notes a 65% passing score.

Q: What should Salesforce Admin flashcards cover?

Salesforce Admin flashcards should cover users and security, object model basics, profiles, permission sets, sharing, automation, reports, dashboards, data management, Sales Cloud, Service Cloud, and setup terminology.

Q: How long should I study for Salesforce Admin?

Most candidates should plan 80-140 hours, especially if they are new to Salesforce setup. Combine flashcards with Trailhead practice and hands-on configuration in a sandbox or Trailhead Playground.

Question 1

Current exam outline

Accepted Answer

Use the current Trailhead Platform Administrator outline as the study map. Older labels like Salesforce Administrator or ADM-201 can help with search, but current Salesforce sources control scope.

Question 2

Closed-reference exam habit

Accepted Answer

Prepare to explain the admin decision without notes. Practice identifying the object, user, data, security layer, automation, and reporting impact before choosing an answer.

Question 3

Exam-dump boundary

Accepted Answer

Do not use, request, or share real certification questions, answers, or superbadge solutions. Study with official resources, hands-on practice, and original scenarios.

Question 4

Credential maintenance

Accepted Answer

Salesforce certifications require annual release maintenance modules. Missing required maintenance can expire the credential, so keep Trailhead contact details and reminders current.

Question 5

Company settings

Accepted Answer

Company settings define org-level context such as fiscal year, business hours, currencies, and locale behavior. These settings influence reporting, scheduling, support rules, and user experience.

Question 6

User record versus license

Accepted Answer

The user record identifies the person; the license controls the broad feature set available to assign. Profiles and permission sets then refine what that licensed user can do.

Question 7

Deactivating a user

Accepted Answer

Deactivation stops login access but preserves owned records and audit history. Before deactivating, plan ownership transfers, queue membership, scheduled jobs, and integrations tied to the user.

Question 8

Login hours

Accepted Answer

Login hours are profile-level controls that restrict when users can access Salesforce. They are useful for business-hour restrictions but must be coordinated with support and integration needs.

Question 9

Session timeout

Accepted Answer

Session timeout controls how long an inactive session can remain open. Shorter timeouts reduce unattended-session risk but can disrupt users doing long-form work.

Question 10

Setup Audit Trail

Accepted Answer

Setup Audit Trail helps administrators review configuration changes made in Setup. Use it when troubleshooting unexpected behavior after admin changes.

Question 11

Profile

Accepted Answer

A profile is the baseline access package assigned to a user, including object permissions, app access, login controls, and other defaults. Each user has one profile.

Question 12

Permission set

Accepted Answer

A permission set grants additional access without changing a user's profile. Use it for exceptions, role-based add-ons, and least-privilege access.

Question 13

Permission set group

Accepted Answer

A permission set group bundles related permission sets so access can be assigned and reviewed as a package. Muting permissions can remove selected permissions from the group.

Question 14

Object permission versus record access

Accepted Answer

Object permission answers whether a user may read, create, edit, or delete that object type. Record access answers which specific records the user can see or modify.

Question 15

Org-wide defaults

Accepted Answer

Org-wide defaults set the baseline record visibility for an object. Sharing rules, role hierarchy, teams, and manual sharing can open access beyond that baseline.

Question 16

Field-level security

Accepted Answer

Field-level security controls whether a user can see or edit a field at all. A field can be on a page layout and still be hidden by field-level security.

Question 17

Role hierarchy

Accepted Answer

The role hierarchy primarily supports record visibility by letting users higher in the hierarchy access records owned by users below them, subject to sharing settings.

Question 18

Record type

Accepted Answer

Record types let one object support different business processes, picklist values, and page layout assignments. Use them when users need distinct experiences on the same object.

Question 19

Page layout

Accepted Answer

A page layout controls field placement, related lists, buttons, and sections for record pages. It affects presentation, not whether the user has underlying field or object permission.

Question 20

Validation rule

Accepted Answer

A validation rule blocks a save when data does not meet business criteria. It protects new and edited data, but it does not automatically repair old bad records.

Question 21

Formula field

Accepted Answer

A formula field calculates its value from other data and is read-only to users. Use it for derived values, not for data that users must manually maintain.

Question 22

Lookup relationship

Accepted Answer

A lookup relationship loosely connects records. The child record can usually exist without the parent unless you make the field required or add other controls.

Question 23

Master-detail relationship

Accepted Answer

A master-detail relationship tightly connects records. The detail inherits ownership and sharing from the master, and deleting the master deletes related detail records.

Question 24

Roll-up summary field

Accepted Answer

A roll-up summary calculates values from detail records onto the master record in a master-detail relationship, such as counts, sums, minimums, or maximums.

Question 25

Lightning App Builder

Accepted Answer

Lightning App Builder configures Lightning pages with components, visibility rules, and page assignments. Use it to tailor the record, app, or home page experience.

Question 26

Dynamic Forms

Accepted Answer

Dynamic Forms move field and section control into the Lightning page so admins can show fields conditionally. Security still depends on field-level security and permissions.

Question 27

App page versus record page

Accepted Answer

An app page provides a workspace or dashboard-like screen in Lightning Experience. A record page controls how users view and act on an individual record.

Question 28

Lead conversion

Accepted Answer

Lead conversion creates or links to Account, Contact, and optionally Opportunity records. Map custom lead fields before conversion so important data carries forward.

Question 29

Opportunity stages

Accepted Answer

Opportunity stages represent the sales process and drive pipeline reporting. Stage values should match business milestones that sales teams can apply consistently.

Question 30

Products and price books

Accepted Answer

Products describe what is sold, and price books define the prices available for those products. Opportunities use opportunity products to capture line-item revenue.

Question 31

Campaign influence

Accepted Answer

Campaigns track marketing efforts and member engagement. Campaign influence helps connect marketing activity to opportunities when the org needs attribution insight.

Question 32

Case assignment rule

Accepted Answer

A case assignment rule routes new cases to users or queues based on criteria. Use it when intake should be distributed automatically instead of manually triaged.

Question 33

Queue

Accepted Answer

A queue holds records for a group until an owner takes or receives them. Queues are common for cases, leads, and shared work intake.

Question 34

Escalation rule

Accepted Answer

An escalation rule raises a case when time-based or criteria-based service conditions are missed. It supports SLA follow-up and should align with business hours.

Question 35

Email-to-Case versus Web-to-Case

Accepted Answer

Email-to-Case creates cases from incoming email. Web-to-Case creates cases from web form submissions. Choose based on the customer's intake channel.

Question 36

Knowledge data categories

Accepted Answer

Data categories organize Knowledge articles and help control which article groups are visible to users or customers. They are especially useful for large knowledge bases.

Question 37

Tasks and events

Accepted Answer

Tasks track to-do work, while events reserve time on a calendar. Both support activity history and sales or service follow-up.

Question 38

Chatter

Accepted Answer

Chatter supports collaboration around records, groups, and updates. It helps users discuss work in context instead of moving record decisions into disconnected channels.

Question 39

Salesforce Mobile readiness

Accepted Answer

Mobile readiness means checking layouts, actions, Lightning pages, compact layouts, and security from a mobile user's workflow, not just confirming that the app opens.

Question 40

AppExchange governance

Accepted Answer

Before installing an AppExchange package, review business need, permissions, data access, support model, sandbox testing, and uninstall impact.

Question 41

Data Import Wizard versus Data Loader

Accepted Answer

Data Import Wizard is web-based and suited to simpler supported-object imports. Data Loader supports broader objects, larger files, and operations such as update, upsert, export, and delete.

Question 42

Upsert

Accepted Answer

Upsert inserts new records and updates existing records in one operation, usually matching on Salesforce ID or an external ID field.

Question 43

Duplicate management

Accepted Answer

Matching rules define what looks like a duplicate. Duplicate rules decide what happens next, such as alerting users or blocking the save.

Question 44

Report format choice

Accepted Answer

Use tabular for simple lists, summary for grouped subtotals, matrix for row-and-column comparisons, and joined reports when separate report blocks need to appear together.

Question 45

Dashboard running user

Accepted Answer

A dashboard's running user affects what data the dashboard can display. Folder access lets users open the dashboard, but record visibility still matters.

Question 46

Flow Builder

Accepted Answer

Flow Builder is the primary declarative automation tool for guided screens, record-triggered logic, scheduled work, and reusable automation. Test flows before activating them.

Question 47

Record-triggered flow

Accepted Answer

A record-triggered flow runs when a record is created, updated, or deleted. Use clear entry criteria so the flow runs only when the business condition applies.

Question 48

Approval process

Accepted Answer

An approval process routes a record for formal review, lock or unlock behavior, and final approval or rejection actions. Use it when human approval is part of governance.

Question 49

Agentforce guardrails

Accepted Answer

Admin-level Agentforce work includes use-case fit, permissions, trusted data grounding, testing, deployment boundaries, monitoring, and escalation paths for low-confidence or sensitive situations.

Question 50

Einstein Trust Layer

Accepted Answer

The Einstein Trust Layer is Salesforce's trust architecture for AI features, including controls such as secure data handling, grounding, masking, and output safeguards.

Free Salesforce Admin Exam Flashcards

Filter by Topic

Jump to Card

About These Salesforce Admin Flashcards

Topics Covered

Frequently Asked Questions

Salesforce Certified Administrator

Explore More Salesforce Certifications

Salesforce Agentforce

Salesforce Certified Advanced Administrator

Salesforce Platform App Builder

Salesforce Platform Developer I

Salesforce Service Cloud Consultant

Salesforce Tableau Certified Associate

More From This Family