Hard points, in one place
The facts and distinctions that the exam keeps testing, and the traps behind wrong answers.
| Item | Limit | Why it matters |
|---|---|---|
| Data Import Wizard | 50,000 | Above that, use Data Loader. Browser based, duplicate matching, limited objects. |
| Data Loader | 5 million | All objects, export all, upsert, hard delete with Bulk API. |
| Recycle Bin and deleted custom fields | 15 days | After that, restore only from a backup. |
| Mass Delete Records | 250 at a time | Setup tool for small cleanups. |
| Field history tracking | 20 fields · 18 mo | 24 months through the API. More fields or longer retention: Field Audit Trail. |
| Field Audit Trail | 60 fields · 10 yr | Shield add-on, compliance retention. |
| Setup Audit Trail | 180 days | Configuration changes. Download to keep longer. |
| Master-detail per object | 2 | A junction object uses both. |
| Web-to-Lead / Web-to-Case per day | 500 / 5,000 | Excess requests are queued, not lost immediately. |
| Shared Activities | 50 contacts | One task or event related to many contacts. |
| Merge accounts, contacts, leads, cases | 3 records | Pick the master and the field values to keep. |
| Campaign hierarchy | 5 levels | Statistics roll up to parents. |
| Dashboard components | 20 | Dynamic dashboards cannot be scheduled for refresh. |
| Add Multiple Users | 10 | For more, Data Loader inserts User records. |
| Sandbox refresh | 1 / 1 / 5 / 29 days | Developer, Developer Pro, Partial Copy (sample data), Full (all data). |
Two separate questions: what can the user do with an object or field (profiles and permission sets), and which records can the user see (sharing).
| Lookup | Master-detail | |
|---|---|---|
| Sharing and owner | Independent, child has an owner | Controlled by parent, no owner on detail |
| Parent deleted | Clear value (default) or block deletion | Children deleted too |
| Required | Optional | Always required |
| Roll-up summary | No (use Flow) | Yes, on the master |
| Limit per object | Up to 40 | 2 |
| Need | Tool |
|---|---|
| Route a new case right away | Assignment rule, or Omni-Channel for push routing with capacity and skills |
| Email the customer automatically | Auto-response rule |
| Act on cases still open after X hours | Escalation rule with business hours |
| Contractual SLA with countdown | Entitlement process with milestones (success, warning, violation actions) |
| Different case statuses | Support process + record type |
| Repetitive multi-step agent work | Macro. Reusable text snippets: Quick Text |
| Hide an article from customers | Channel visibility. Hide from some agents: data category visibility |
| Different defaults per inbox | One Email-to-Case routing address each |
| Requirement | Answer |
|---|---|
| Block a save and show an error | Validation rule |
| Set fields on the same record | Before-save flow (Fast Field Updates) |
| Create or update other records, send email, post | After-save flow (Actions and Related Records) |
| Do something X days before or after a date | Scheduled path in a record-triggered flow |
| Nightly batch on many records | Schedule-triggered flow, filter in Start |
| User-guided wizard | Screen flow (page, quick action, utility bar) |
| React to an external event | Platform event-triggered flow |
| Sign-off with lock, recall, multi-step approvers | Approval process (submit from Flow if automatic) |
| Multi-stage, multi-team process | Flow Orchestration |
| Logic Flow cannot express or very high volume | Apex, invoked from Flow as an action |
| Term | What to remember |
|---|---|
| Topic | A job to be done: classification description (used to pick the topic), scope, instructions, and its actions. |
| Action | What the agent can execute: flow, invocable Apex, prompt template, standard actions. |
| Agent user | The agent runs as a user; permission sets, FLS and sharing apply. Least privilege. |
| Prompt Builder | Templates: Sales Email, Field Generation, Record Summary, Flex. Must be activated; users need the prompt template permission set. |
| Grounding | Merge fields, related lists, flows, Apex, retrievers. The model is not trained on your data. |
| Einstein Trust Layer | Secure retrieval, data masking, zero data retention, toxicity detection, audit trail. |
| Retrieval (RAG) | Knowledge or a data library; unstructured content relies on Data Cloud. |
| Testing | Conversation preview with reasoning details; Testing Center for batch tests. |
| Channels | Messaging for In-App and Web, routed by Omni-Channel; escalate to a human through Omni-Channel. |