Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Salesforce Admin Practice: Scenarios and Exam Skills

Practice real Salesforce admin decisions: choose the right automation, report format, sandbox, data tool and deployment path, with scenario drills, a study plan and a JavaScript quiz runner.

You now know the tools of this half of the Salesforce administrator's job: Flow, reports and dashboards, data management, sandboxes and deployment. The final skill is choosing. In real work and in certification exams (such as Salesforce Certified Platform Administrator), questions rarely ask for a definition. They describe a business situation and ask what you should do. This lesson gives you scenarios to practice that thinking, a method for answering, a study plan and a small runner for your own question bank.

This lesson is independent of any real exam content: the scenarios are original and are not taken from any exam. Salesforce changes features each release, so confirm details in the current release notes and Help. The demonstrations are JavaScript stand-ins and not Salesforce.

A method for scenario questions

  1. Find the requirement: what must happen, for whom, and when?
  2. Find the constraints: user count, data volume, edition, "no code", time, security, who maintains it.
  3. Pick the simplest tool that satisfies both. Order of preference: standard configuration, then Flow, then a packaged app, then Apex code.
  4. Check limits and side effects: governor limits, permissions, who sees what, effect on other automation.
  5. Plan the test and the deployment: sandbox, test users, change set, rollback.

Scenario drills

Try to answer each before reading the suggested answer.

1. A manager wants the field "Region" filled automatically from the account's country whenever an opportunity is created. A before-save record-triggered flow on Opportunity: Get the account's country (or use a formula field if the value is directly on a parent) and set {!$Record.Region__c}. A formula field would work if no reps need to override it.

2. Reps should answer a six-question qualification script when they click a button on a lead. A screen flow launched from a quick action on Lead, creating or updating records at the end.

3. Every night, close cases that have waited on the customer for 14 days. A schedule-triggered flow over Cases with Status = Waiting on Customer and LastModifiedDate older than 14 days; one Update Records after any loop.

4. A report must list accounts that have no open opportunities. A summary or tabular report with a cross filter: Accounts WITHOUT Opportunities where IsClosed = False. (See Filters, buckets and formulas.)

5. Regional managers must see their own region on the same dashboard. A dynamic dashboard (run as the logged-in user), or a dashboard filter by Region with a fixed running user when everyone may see all data. The decision depends on whether viewers may see each other's data.

6. You must load 600,000 historical orders and keep them in sync monthly with an ERP key. The Data Loader (or Bulk API) with upsert on an external ID. (See Importing data and the Data Loader.)

7. A mass update wrongly set 3,000 opportunities to Closed Lost an hour ago. Use field history (if tracked) to get the old values, fix with a Data Loader update; otherwise restore from a backup. Then add a flow test and limit who can run mass updates. (See Backup, export and recovery.)

8. Testers need realistic data and 20 users to check a new process for two weeks. A Partial Copy sandbox with a sandbox template (or a Full one if volume or relationships matter); mask personal data.

9. A new field and flow must go to production; one component was forgotten and the deployment failed. Add the missing dependency to the change set, upload again, validate, then deploy; add a deployment checklist. (See Change sets and deployment.)

10. Users complain that the Account page is too long. Convert to Dynamic Forms, use tabs and sections with visibility rules, and trim the related lists. (See Lightning apps, App Builder and pages.)

JS Stand-in: a scenario recommender

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Topics to review

Make a checklist and rate yourself 1 to 5 on each: Org setup and objects (fields, relationships, record types, page layouts), Security (profiles, permission sets, sharing model, field-level security, roles), Automation (flows, approvals, validation rules), Data (import, export, duplicates, backups), Analytics (report types and formats, dashboards, running user), Deployment (sandboxes, change sets), User experience (apps, App Builder, Path, list views), Service and sales features (cases, queues, leads, opportunities, forecasts), and Release management (reading release notes, testing releases in a sandbox preview).

Study plan

  1. Week 1 and 2: read official documentation for each domain; do the corresponding Trailhead modules and build the project in a free Developer Edition org.
  2. Week 3: rebuild this chapter's projects from scratch without notes. Debug every error you meet.
  3. Week 4: practice questions; for each wrong answer, write the rule in one sentence and the doc page where you verified it.
  4. Last days: revisit your sentences; sleep well. Do not memorize numbers that change; learn the reasoning.

Keep a personal admin handbook: limits, naming conventions, deployment checklist, your standard flow skeleton with a fault path.

Habits of an admin people trust

  • Ask "what problem are we solving?" before building.
  • Prefer simple, documented, reversible changes.
  • Test as users, not as yourself.
  • Communicate before and after changes.
  • Read the release notes three times a year.
  • Keep data clean, permissions tight and backups tested.

Stand-in: your own practice quiz

JS Stand-in: a quiz runner for your question bank

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the best first step when answering a scenario question?

    The right tool follows from the requirement and the constraints.
  2. 2. Order of preference for solving a business problem on the platform:

    Use the simplest maintainable tool first.
  3. 3. Why practice rebuilding projects from scratch?

    Doing the work reveals the details you only thought you knew.
  4. 4. How should you treat limits and numbers that change between releases?

    Learn the reasoning, and verify numbers in current Help.

Summary

  • Solve scenarios by identifying the requirement and constraints, choosing the simplest suitable tool, and checking limits, security and deployment.
  • Review every domain: setup, security, automation, data, analytics, deployment and user experience.
  • Practice by rebuilding projects, keeping a handbook, and testing as real users.
  • Verify changing numbers in current Salesforce documentation.

Next: Back to the Salesforce Administration track