Sign in
Home/Salesforce/Salesforce Certified Administrator (ADM-201)/Free questions

Salesforce Certified Administrator (ADM-201) — Free Practice Questions

10 free sample questions from a bank of 598, with the correct answers and explanations. No signup required — start practising right now.

1Inline editing updates the field when
  • The field is saved/updated
  • When the record is saved/updated
  • When the return key is pressed
  • None of the above
Answer: A

The short version

A — Inline editing saves the field itself when committed. List-view and record edits apply at field level without a full record save. The settled key is A because the field update is the save event.

Key concepts in this question

  • Inline editing: direct change from list view or detail hover without opening edit layout.
  • Field-level save: committing that cell writes the value immediately to the database.
  • Record save: full edit-mode save that validates all fields, not required here.
  • Return key: keyboard shortcut that may commit the cell but is not the rule itself.
  • None of the above: distractor when a direct field commit exists.

Why A is correct

A is correct because Salesforce commits an inline edit as soon as the user confirms that field, updating storage for that column. No separate record-save click is needed when the pencil edit is applied. That matches the vendor note that committing the inline edit is the save action, so the field-save choice describes reality.

Why the others are wrong

  • B. Full record save is for edit layouts; inline edits do not wait for that broader save.
  • C. Return key may confirm entry but the save principle is field commit, not a specific key.
  • D. None of the above fails because a valid field-save behavior is documented.

ADM-201 exam tip

For inline editing think field saves itself on commit; no full record save is needed.

2User interface settings are global settings and apply to all users of an org.
  • True
  • False
Answer: A

The short version

A — User interface settings are global and apply to all users. Theme, sidebar and accessibility options sit at org level. The settled key is A because True reflects that org-wide scope.

Key concepts in this question

  • User interface settings: setup area for collapsible sections, hover details and accessibility mode.
  • Global scope: org-wide defaults that shape display for every user session.
  • Profiles: control object access, not the shared UI chrome covered here.
  • Personal settings: individual language or display tweaks that layer atop global UI baselines.
  • True versus False: test of whether UI settings vary per user or apply broadly.

Why A is correct

A is correct because Salesforce documents user-interface settings as global controls determining how all users view and access interface features. Enabling collapsible sidebar or hover behavior changes the experience org-wide rather than per profile. That global application is why the True statement matches the settled key. Admins set these once in Setup and every profile inherits the same chrome, which simplifies support and training across the org.

Why the others are wrong

  • B. False would mean per-user scoping, which contradicts the documented org-wide UI settings behavior.

ADM-201 exam tip

When you see user interface settings think global org defaults for all users.

3Custom Links can be used for the following:
  • Launching an External URL
  • Running an S Control
  • Running a report
  • All of the Above
Answer: A

The short version

A — Launching an External URL. S-Controls no longer exist on the platform, so the 'All of the Above' option cannot be true; a custom link still launches any URL.

Key concepts in this question

  • Custom link: A named URL shortcut added to a tab, app menu, or record page. It can target an external site, an internal report URL, a Visualforce page, or a flow.
  • S-Control: The legacy Flash/Java control technology, retired in API 26 and removed. No link can launch one in a current org.

Why A is correct

A custom link is nothing more than a labelled URL, so pointing it at an external website is the defining use case. The exam trap is the S-Control option: because that technology was removed from Salesforce, the 'All of the Above' choice is invalid no matter how many of the other options are true.

Why the others are wrong

  • B. S-Controls were retired and removed from the platform; a link cannot launch one.
  • C. Links can also open an internal report URL, but this item is single-answer and the dead S-Control option removes 'All of the Above' from play, leaving the unambiguous capability.
  • D. Fails as soon as one of its parts (S-Controls) is impossible.

ADM-201 exam tip

If an option names a retired technology (S-Controls, Paperwork, Silver), the 'All of the Above' it sits inside is wrong — read the sub-options before you accept D.

4When creating users, does the alias need to be unique?
  • Yes
  • No
Answer: B

The short version

B — Alias does not need to be unique when creating users. Username must be globally unique while alias is a short display label. The settled key is B because No matches that documented rule.

Key concepts in this question

  • Username: globally unique logon in email format that identifies the user across Salesforce.
  • Nickname and alias: short labels for community and list display that may repeat under this bank key.
  • Uniqueness scope: only username is enforced unique at creation in this question logic.
  • Trailhead reference: user-setup module that lists required unique fields for new users.
  • Yes versus No: test of whether duplicate aliases are rejected or allowed.

Why B is correct

B is correct because the settled key treats username as the unique gate while alias can repeat across users. Admins can reuse short aliases for people with similar names without violating creation rules. The vendor note points to Trailhead user setup where username uniqueness is the blocker, so No is the expected answer.

Why the others are wrong

  • A. Yes would enforce alias uniqueness, which this bank key does not require for user creation.

ADM-201 exam tip

For user creation memorize username unique globally while alias may repeat per this key.

5When using Territory Management, can an opportunity be associated with multiple territories?
  • Yes
  • No
Answer: B

The short version

B — An Opportunity links to only one territory under this bank key. Legacy territory management ties revenue to a single territory for forecasting. The settled key is B because No reflects that one-territory model.

Key concepts in this question

  • Territory Management: assignment of accounts and reps to sales areas for coverage.
  • Opportunity territory: revenue attribution used for forecasts and quota in the legacy model.
  • Single assignment: design where each Opportunity carries one territory to keep forecasting clean.
  • Accounts and users: entities that may span multiple territories even when Opportunities do not.
  • Yes versus No: test of whether multi-territory Opportunities are allowed in this version.

Why B is correct

B is correct because the settled explanation states Opportunities can only be in one territory while accounts and users may span many. That preserves a single forecast owner per deal and avoids double counting. Later Enterprise Territory models add flexibility, but this bank row follows the single-territory rule, so No is the explained key.

Why the others are wrong

  • A. Yes would allow multi-territory Opportunities and break single-forecast ownership under this key.

ADM-201 exam tip

For legacy territory questions default Opportunity to one territory; accounts and users may span many.

6Do users have to display the jump page every time they create a new record?
  • Yes
  • No
Answer: B

The short version

B — Users need not see the jump page on every new record. They can accept a default record type and skip selection. The settled key is B because No captures that bypass.

Key concepts in this question

  • Record types: variations of an object with different picklists and layouts.
  • Jump page: intermediate selector that asks which record type to use during create.
  • Default record type: profile-level choice that lets users proceed without prompting.
  • Prompt every time: behavior only when no default is set or user must choose.
  • Yes versus No: test of whether the selector is mandatory.

Why B is correct

B is correct because Salesforce lets users set a profile default so new-record creation goes straight to the edit page. The jump page appears only when multiple types exist without a default or when the user chooses to be prompted. Allowing the default therefore removes the every-time requirement, matching the No key. Admins can still force prompting by leaving defaults blank, but standard users with defaults proceed directly to fast creation.

Why the others are wrong

  • A. Yes would force the selector on every create, ignoring the profile default bypass.

ADM-201 exam tip

If a profile has a default record type the jump page can be skipped on create.

7If I'm looking at a detail page, do I know what record type it is?
  • Yes
  • No
Answer: B

The short version

B — Detail page alone does not reveal its record type under this bank key. Type may hide when layouts match or the field is absent. The settled key is B because No reflects that limited visibility.

Key concepts in this question

  • Detail page: record view showing fields and related lists per assigned layout.
  • Record type: category that can drive picklists and layouts behind the scenes.
  • Type indicator: explicit field or distinct layout cue needed to know the type.
  • Identical layouts: setup where different types share the same page, hiding the distinction.
  • Yes versus No: test of whether viewing details guarantees type knowledge.

Why B is correct

B is correct because without a record-type field on the layout or a visibly different page, the detail view gives no reliable signal. Admins can assign the same layout to several types, so users cannot infer type from content alone. That is why the settled key answers No rather than assuming always-visible typing. Only an explicit type field or a clearly distinct layout gives certainty, so detail content alone is insufficient proof.

Why the others are wrong

  • A. Yes would require every detail to expose type, which fails when layouts match or the field is hidden.

ADM-201 exam tip

Do not assume type from detail alone; look for the record-type field or distinct layout.

8Universal Containers sells their products to wholesale partners and retail outlets. Each process has its own set of unique sales stages. Which three features can an administrator customize for each opportunity stage? (Choose three.)
  • Quota
  • Probability
  • Product Family
  • Forecast Category
  • Type
Answer: B, D, E

The short version

BDE — Probability, Forecast Category, Type. Those three are the per-stage settings on the Opportunity stage configuration; quota is a per-user/per-period target and Product Family is a product attribute.

Key concepts in this question

  • Opportunity stage value settings: Setup > Object Manager > Opportunity > Stage > Opportunity Stages Picklist Values. Each value carries a Type (Open, Closed Won, Closed Lost), a Probability and a Forecast Category, plus a description.
  • Sales process: The ordered, filtered subset of those stage values that defines the pipeline for a record type.
  • Quota: The monthly or quarterly goal assigned to a user or territory and entered on the Forecasts quota page — never per stage.
  • Product Family: A field on Product used to group opportunity products for forecasting; not a stage attribute.

Why BDE is correct

Two teams with different pipelines still share the Opportunity Stage field, so everything an admin tunes 'for each opportunity stage' lives on the stage value itself: whether the stage is open or closed (Type), how likely it is to close (Probability), and which forecast bucket it feeds (Forecast Category). Quota is the classic distractor because it is a real forecasting object, but it is assigned per user or territory per period, so it cannot vary by stage.

Why the others are wrong

  • A. Quota is a user/territory-level goal entered in Forecasts settings, not a property of a stage.
  • C. Product Family belongs to products sold on the opportunity; changing it does not change the stage.

ADM-201 exam tip

Per-stage = Type, Probability, Forecast Category. Per-period = Quota. Never mix the two lists.

9Universal Containers has purchased additional licenses for five new sales representatives that will start in 30 days. The email accounts for the new representatives will not be active until they start. The new users should be set up ahead of time to assign records, list views, and other Salesforce utilities needed on the day they start. Which method should a System Administrator use to set up the new users without sending a notification?
  • Create new users, and then set the start date for 30 days ahead.
  • Create new users, and then assign a permission set with a start date for 30 days ahead.
  • Create new users, and then Freeze the users.
  • Create new users, and uncheck Generate new password, and notify the user immediately.
Answer: D

The short version

D — Create the users and uncheck 'Generate new password and notify user immediately'. That checkbox is the only switch that controls the notification email, which matters because these reps' mailboxes are not live yet.

Key concepts in this question

  • New User page: Setup > Users > New User. The password block has a checkbox 'Generate a new password and notify user immediately'; unticking it lets the admin set the password and sends nothing.
  • Why the scenario matters: The reps' email accounts do not exist for 30 days, so an invitation email would bounce — the notification must be suppressed, not delayed.
  • Not a real feature: Users have no 'start date' field; you cannot schedule when the notification goes out.

Why D is correct

The requirement is 'set up the users ahead of time without sending a notification', and the notification is controlled by exactly one checkbox on the New User page. Creating the user with that box cleared leaves the account ready — profile, role, sharing, permissions all assigned — with no email generated, which is exactly what the reps' inactive mailboxes require.

Why the others are wrong

  • A. There is no user start-date setting in Setup; nothing about creating a user defers the email.
  • B. Permission sets have no start date, and permission sets do not govern the notification email.
  • C. Freezing blocks login but still leaves the welcome email being sent, so it does not satisfy 'without sending a notification'.

ADM-201 exam tip

The New User password checkbox is your mute button: untick 'notify user immediately' to pre-provision a user silently.

10It is possible to share a custom object record manually
  • True
  • False
Answer: A

The short version

A — Manual sharing works for custom-object records. Owners, hierarchy superiors and admins can share individual rows. The settled key is A because True matches that sharing toolkit.

Key concepts in this question

  • Manual sharing: row-level Share button that grants access outside OWD and rules.
  • Custom objects: admin-defined tables that support sharing models like standard objects.
  • Role hierarchy: grants superiors of the owner implicit rights including manual shares.
  • OWD plus sharing rules: baseline plus automated grants that manual sharing complements.
  • True versus False: test of whether custom rows can ever be shared by hand.

Why A is correct

A is correct because Salesforce permits manual sharing on custom objects when OWD is not public read-write. The record owner, anyone above in the role hierarchy and admins can use the Sharing button to extend read or edit to others. That hand-grant path is explicitly part of the sharing story alongside rules and hierarchy. It is ideal for exceptions where automated rules are too broad yet the record must be visible to a chosen peer or manager.

Why the others are wrong

  • B. False would deny a documented Share-button capability that custom objects support.

ADM-201 exam tip

Remember custom-object rows support manual shares by owner, hierarchy and admin.

Want the full bank of 598 questions for Salesforce Certified Administrator (ADM-201)? See all practice exams.