ADM-201 domain - 10% of the exam

Productivity and Collaboration

Productivity and Collaboration is 10% of the ADM-201 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

30
Practice questions
2
Objectives
14
Easy
16
Medium

Where people go wrong

  • Using a global action where the record must be linked

    The wrong answers reach for a global action when the new Task should attach itself to the Account or Work Order the user is viewing. A global action is not tied to any record, so it does not relate the new record to its parent. An object-specific action runs in the context of its record, pre-relates the new record, and can carry a predefined field value such as a fixed Subject. The reverse slip also fails: an object-specific action lives on one object's layouts and cannot reach the Home page.

    See it in a sample question
  • Mixing up compact layouts with other layout features

    A compact layout is credited with jobs that belong elsewhere: arranging the detail page, setting actions, or controlling mobile navigation. The wrong answers also send the problem to the page layout, mini page layouts or search layouts. A compact layout only defines the key fields shown, in order, in the highlights panel and on mobile record cards. The full detail page comes from the page layout, and mobile navigation comes from the Lightning app's navigation items.

    See it in a sample question
  • Confusing a task with an event

    The wrong answers swap the two activity types. An event is a scheduled block of time with a start and an end that sits on the calendar. A task is a to-do with a due date and a status, shown under Upcoming and Overdue until it is completed. A recurring task still has no start and end time, and an event with invitees is a shared calendar entry, not separate to-dos owned by each person.

    See it in a sample question
  • Treating Chatter as a way to grant access

    The wrong answers read Chatter features as security or ownership controls. Following a record only subscribes the user to that record's feed updates. It does not transfer ownership or change who can see the record. Chatter is a collaboration tool and is separate from sharing rules, which control record access. Access still comes from the sharing model, not from posts, groups or follows.

    See it in a sample question
  • Choosing the wrong tool for a personalised email

    The wrong answers offer an email alert or Quick Text where an email template with merge fields fits, or a text or Visualforce template where branding and non-admin authoring are required. An alert sends automatically on criteria rather than on demand. Quick Text does not resolve record merge fields such as the Case number. A text template supports merge fields but carries no branding, and Visualforce needs development skills. A Lightning email template with an enhanced letterhead gives branded, merge-field emails that non-admins can build.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleProductivity and Collaborationmedium

At Yallingup Wines, field reps use the Salesforce mobile app and need a fast way to log a call from an open Account so that a completed Task is created and automatically linked to that Account, with the Subject pre-set to "Site visit". The administrator wants the least-effort declarative option that works on the Account record page. What should the administrator create?

  • AA global quick action of type Log a Call with a predefined Subject, added to the Global Publisher Layout.
  • BA custom detail-page button on Account that opens a prefilled Task edit page.
  • CAn object-specific action on Account of type Log a Call with a predefined field value setting the Subject, added to the Account page layout. Correct
  • DA record-triggered flow on Account that inserts a Task when the record is edited.
Object-specific quick actions auto-relate the created record to the host record and support predefined field values. Because an object-specific action runs in the context of the record it sits on, Salesforce sets the relationship field on the new Task automatically, and predefined field values populate the Subject, so one Log a Call action on the Account layout satisfies the create, link, and prefill needs in the mobile app.

Why A is wrong: A global action can create a Task and is tempting for reuse across objects, but launched globally it does not automatically associate the Task with the specific Account record, so the linking requirement fails.

Why B is wrong: Classic custom buttons that build a URL are not supported in the Salesforce mobile app and would not present the reps a working action there, so this does not meet the mobile requirement.

Why C is correct: An object-specific Log a Call action automatically relates the resulting Task to the Account it is launched from and supports a predefined field value for Subject, meeting every requirement with a single declarative action.

Why D is wrong: A record-triggered flow fires on save rather than giving reps a button to log a call on demand, so it does not provide the quick manual logging action the scenario asks for.

Free sampleProductivity and Collaborationmedium

What does a compact layout control on a Salesforce object?

  • AThe full set of fields, buttons, and related lists shown on a record's detail page in Lightning Experience.
  • BThe quick actions that appear in the action bar when a user opens a record in the Salesforce mobile app.
  • CThe fields a user is permitted to edit, based on the profile or permission set assigned to that user.
  • DThe key fields displayed in the highlights panel at the top of a record and on record cards in the Salesforce mobile app. Correct
A compact layout sets the key fields shown in the highlights panel and on Salesforce mobile record cards. Compact layouts drive the summary view of a record: the highlights panel in Lightning and the top fields on mobile cards. They do not govern full-page fields, actions, or field-level security, which are handled by page layouts and the security model.

Why A is wrong: This is tempting because compact layouts and page layouts both organise fields, but the detail page fields, buttons, and related lists are governed by the page layout, not the compact layout.

Why B is wrong: Actions in the mobile action bar come from the actions section of the page layout, not the compact layout, so this confuses two separate configuration areas.

Why C is wrong: Editability by user is set through field-level security on profiles and permission sets, so this describes access control rather than what a compact layout does.

Why D is correct: A compact layout defines the priority fields surfaced in the Lightning highlights panel and on mobile record cards, giving users a quick summary without opening the full layout.

Free sampleProductivity and Collaborationeasy

At Kalbarri Consulting, an account manager needs to block a two-hour client meeting for next Tuesday that shows on her Salesforce calendar with a defined start and end time and is linked to the client's Account. Which activity should she create?

  • AA task with a due date of next Tuesday related to the Account.
  • BAn event with a start and end time related to the Account. Correct
  • CA Chatter post on the Account announcing the meeting time to colleagues.
  • DA recurring task series set to repeat each Tuesday on the Account.
Choose an event, not a task, when an activity needs a defined start and end time on the calendar. Events are time-bound activities with start and end times that render on the Salesforce calendar, whereas tasks are to-do items with only a due date, so a timed meeting must be an event.

Why A is wrong: A task is a to-do with a due date but no time slot, so it will not occupy a start-to-end block on the calendar the way a scheduled meeting requires.

Why B is correct: An event is the activity type that has a start and end time and appears on the Salesforce calendar; relating it to the Account links it to the record, meeting every part of the requirement.

Why C is wrong: A Chatter post communicates information but is not an activity with a scheduled time and does not appear on the calendar, so it does not block the meeting.

Why D is wrong: A recurring task still lacks a start and end time and would create repeating to-dos rather than a single timed calendar block, so it does not fit a one-off timed meeting.

Free sampleProductivity and Collaborationeasy

In Chatter, what is the effect of a user choosing to follow a record such as an opportunity?

  • AThe user is granted edit access to the record even if the sharing model would otherwise make it read-only for them.
  • BThe record is automatically reassigned to the user, making them the new owner and recipient of related tasks.
  • CThe user receives updates about that record's feed activity in their Chatter feed without changing who owns or can access it. Correct
  • DAll other users in the org are notified that the record now requires their attention and immediate review.
Understand that following a record subscribes a user to its feed without altering access or ownership. Following in Chatter is a personal subscription that pushes a record's feed updates to the follower's feed, which is a collaboration convenience and deliberately independent of the sharing and ownership model.

Why A is wrong: Following is a feed subscription and never changes record access; access is still governed by the sharing model, so this confuses collaboration with security.

Why B is wrong: Following never transfers ownership; this confuses a feed subscription with record reassignment, which is a separate administrative action.

Why C is correct: Correct: following subscribes the user to the record's feed updates in their own Chatter feed and has no effect on ownership or access.

Why D is wrong: Following notifies only the follower through their own feed, not the whole org, so this overstates the reach of the subscription.

Free sampleProductivity and Collaborationmedium

At Geraldton Media, the support team wants a reusable email that greets each customer by their first name and inserts the related Case number automatically when a rep sends it from a Case record, so reps do not retype these details. Which feature should the administrator use to build this?

  • AA text email template that uses merge fields for the contact name and the Case number. Correct
  • BAn email alert action configured within a record-triggered flow on the Case object.
  • CA quick text entry containing the greeting and a placeholder for the Case number.
  • DA validation rule on the Case object that populates the greeting text when the record is saved.
Email templates use merge fields to auto-populate recipient and record data into a reusable message at send time. Email templates are designed to be reused and to insert record data through merge fields, so the contact first name and the related Case number are resolved from the record when the rep sends the email, removing manual retyping.

Why A is correct: Email templates support merge fields that pull data such as the contact's first name and the related Case number at send time, giving the reusable, auto-populated email the team needs.

Why B is wrong: An email alert sends automatically based on criteria rather than being composed and sent on demand by a rep, so it does not fit a rep choosing to send a personalised email from the record.

Why C is wrong: Quick Text inserts reusable snippets into a message, but it does not resolve record merge fields like the Case number automatically, so the rep would still have to fill in the details by hand.

Why D is wrong: Validation rules only block saves that fail a condition and cannot populate or send email text, so this choice misunderstands what the feature does entirely.

Other domains in this exam

See also the ADM-201 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.