Free Salesforce Admin Exam Flashcards

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.

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

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

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

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.

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.

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.

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.

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.

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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.

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

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

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

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

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.

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

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.

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.

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.

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

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

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.

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

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.

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

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

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.

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

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

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.

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.

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.

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