ADM-201 domain - 15% of the exam

Object Manager and Lightning App Builder

Object Manager and Lightning App Builder is 15% of the ADM-201 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

45
Practice questions
3
Objectives
45
Medium

Where people go wrong

  • Swapping master-detail and lookup behaviour

    The wrong answers hand cascade delete to a lookup, give a detail record its own owner and sharing, or give a lookup the required, locked parent of master-detail. Those traits are reversed. In a master-detail relationship the detail record is deleted with its master, has no owner field and inherits sharing from the master. A lookup is loosely coupled: children are retained by default when the parent is deleted, the field can be left empty, and the child keeps its own sharing.

    See it in a sample question
  • Placing a roll-up summary on a lookup or the wrong side

    The wrong answers offer a lookup, an external lookup, a hierarchical relationship, a formula field or a roll-up field on the child object as the way to total child values. A roll-up summary field can be created only on the master side of a master-detail relationship, so a lookup must be converted first. It supports COUNT, SUM, MIN and MAX only; average and median are not available operations.

    See it in a sample question
  • Using field security or layouts to filter picklist values

    The wrong answers reach for field-level security, a validation rule, a page layout or deactivating a value when only some picklist values should be offered. Field-level security governs access to the whole field, a validation rule blocks a value only after it is chosen, and deactivation removes the value from every record type. Record types hold the list of available values, so a newly added value must also be included in each existing record type, such as Premier Support.

    See it in a sample question
  • Using validation rules, flows or field security to show components

    The wrong answers use a validation rule, a flow, field-level security or an extra record type to make a field or component appear on a Lightning page. Validation rules run on save, flows change data, and field-level security governs access to the data. Dynamic Forms and component visibility filters decide what is displayed, based on field values such as Status or Priority, so the field or component shows only when the condition holds.

    See it in a sample question
  • Confusing app pages, home pages and record pages

    The wrong answers offer a record page, a home page or the utility bar when a standalone page is needed. A record page is bound to one record of an object. A home page is the app's landing screen, not a separate item added to the navigation bar. The utility bar docks small tools in the footer. An app page is not tied to any record and can be added to a Lightning app's navigation as its own tab, holding components such as report charts and list views.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleObject Manager and Lightning App Buildermedium

How does deleting a parent record differ between a master-detail relationship and a lookup relationship when related child records exist?

  • AIn both relationship types the child records are automatically deleted along with the parent record.
  • BIn both relationship types the child records are retained and the relationship field is simply cleared.
  • CIn a master-detail relationship the child (detail) records are deleted with the parent, whereas in a lookup relationship the children are retained by default. Correct
  • DIn a lookup relationship the child records are deleted with the parent, whereas in a master-detail relationship they are retained.
Understand that master-detail cascades deletion to child records while a lookup retains them by default. Master-detail is tightly coupled so a detail record cannot exist without its master, which forces a cascade delete of children, whereas a lookup is loosely coupled and leaves child records untouched when the parent is removed.

Why A is wrong: This is tempting because both relationships link a child to a parent, but only master-detail cascades the delete. A lookup does not delete its child records by default.

Why B is wrong: This describes only the lookup behaviour. In a master-detail relationship the detail records cannot survive without their master, so they are cascade-deleted rather than retained.

Why C is correct: Master-detail is a tightly coupled relationship where the detail record cannot exist without its master, so deleting the master cascades the delete to the children, while a standard lookup leaves the child records in place.

Why D is wrong: This reverses the two behaviours. Cascade delete belongs to master-detail because of its tight coupling, not to the loosely coupled lookup relationship.

Free sampleObject Manager and Lightning App Buildermedium

Which set of calculations can a roll-up summary field perform on the related detail records?

  • AAverage of a chosen number field, and concatenation of the text values across the detail records.
  • BCount of records, and the sum or average of a chosen number, currency, or checkbox field.
  • CMedian and mode of a chosen number field, and a count of the related detail records.
  • DCount of records, the sum of a number or currency field, and the minimum or maximum of a number, currency, or date field. Correct
Know that roll-up summary fields support COUNT, SUM, MIN, and MAX, not average or text operations. A roll-up summary field aggregates detail records using COUNT, SUM on a number, currency, or percent field, and MIN or MAX on a number, currency, percent, or date field, and it offers no average, median, mode, or text concatenation function.

Why A is wrong: Roll-up summaries do not offer an average or text concatenation. AVG must be derived from SUM divided by COUNT, and text fields cannot be rolled up.

Why B is wrong: AVG is not a roll-up summary operation and checkbox fields cannot be aggregated, so this set is not one the feature actually supports.

Why C is wrong: Median and mode are not available roll-up summary operations. The supported functions are COUNT, SUM, MIN, and MAX only.

Why D is correct: A roll-up summary supports COUNT of detail records, SUM on a number, currency, or percent field, and MIN or MAX on a number, currency, percent, or date field. SUM does not apply to date fields, whereas MIN and MAX do, which is exactly the aggregation set available.

Free sampleObject Manager and Lightning App Buildermedium

An administrator wants only a subset of a picklist field's values to be selectable on records of one particular record type. Which approach achieves this?

  • AAssign only the desired picklist values to that record type in the record type's picklist value configuration. Correct
  • BAdjust field-level security for the picklist field on the relevant profiles so the unwanted values are hidden.
  • CCreate a validation rule that returns an error whenever one of the unwanted values is chosen on that record type.
  • DDeactivate the unwanted values on the field definition so that no record type can present them.
Record types restrict which picklist values are available on records of that type without changing the field globally. Each record type stores its own selected set of values for a picklist field. Assigning only the desired values to the record type limits the choices for records of that type while leaving the master value set and other record types untouched.

Why A is correct: Correct. Editing a record type lets the administrator include only chosen values for a picklist field, so records of that record type present just that subset.

Why B is wrong: Field-level security controls access to the whole field, not to individual picklist values, so it cannot restrict specific values per record type, making this wrong.

Why C is wrong: A validation rule can block a value after selection, but the value still appears in the list; the intended mechanism controls which values are offered, so this is not the best answer.

Why D is wrong: Deactivating a value removes it globally from every record type, which is broader than the requirement to limit values on one record type only, so this is wrong.

Free sampleObject Manager and Lightning App Buildermedium

At Geraldton Utilities, an administrator must show a Rich Text instructions component on the Case Lightning record page only when the Case Priority field equals High, and hide it for every other priority. What is the most appropriate way to control this display in the Lightning App Builder?

  • ARestrict the component by adjusting field-level security on the Priority field for the affected profiles.
  • BAdd a component visibility filter on the Rich Text component that shows it only when Priority equals High. Correct
  • CCreate a validation rule that fires whenever the Priority field is not set to High.
  • DAssign a separate Lightning record page for each Priority value through app-default activation.
Component visibility filters show or hide a single Lightning page component based on the record's field values. A component visibility filter is set on the individual component in the Lightning App Builder and is evaluated against the current record's field values as the page loads, which is exactly the run-time, per-field-value show-or-hide behaviour the requirement describes.

Why A is wrong: Field-level security governs whether users can read or edit the Priority field itself; it never decides whether a separate Rich Text component is rendered, so it cannot meet the requirement.

Why B is correct: Component visibility filters evaluate the record's field values at run time, so a single filter of Priority equals High renders the Rich Text component only for high-priority Cases and hides it otherwise.

Why C is wrong: Validation rules block a save when a condition is met, which sounds relevant because it evaluates Priority, but they do nothing to show or hide a component on the page.

Why D is wrong: Page assignment can vary by app, record type and profile but cannot switch on an arbitrary field value such as Priority, so this both over-builds and fails the requirement.

Free sampleObject Manager and Lightning App Buildermedium

Which statement correctly describes a Lightning app page built in the Lightning App Builder?

  • AIt is a single-page destination added to the navigation bar or mobile navigation menu for a focused task or set of components. Correct
  • BIt overrides the fields shown in a record's detail area for a chosen record type and profile combination.
  • CIt defines the field arrangement used on the create and edit screens for a specific object.
  • DIt is displayed automatically whenever a user opens any record of the associated object.
A Lightning app page is a standalone, component-based page reached from the navigation bar or mobile menu, not tied to any record. App pages are one of the three Lightning page templates; they present a curated set of components for a focused task and are accessed through the app navigation bar or the mobile navigation menu, unlike record pages that render in the context of a specific record.

Why A is correct: An app page is a standalone page composed of components and surfaced through the navigation bar in Lightning Experience or the navigation menu in the mobile app for a specific purpose.

Why B is wrong: This describes a Lightning record page assignment, not an app page; app pages are not tied to a single record's detail area.

Why C is wrong: This is tempting because both involve field display, but create and edit screens are driven by page layouts, whereas an app page hosts a task-focused set of components.

Why D is wrong: That behaviour belongs to a record page assigned to an object; an app page is opened deliberately from navigation and is not bound to a record.

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.