Object Manager and Lightning App Builder — Salesforce Platform Administrator practice questions

What is a roll-up summary field?

1. A field that copies a single value down from the parent onto each child record
2. A parent-side field aggregating count, sum, min or max across detail records
3. A formula field that calculates a result from other fields on the same record
4. A report grouping that subtotals rows without storing anything on the record
5. A picklist whose values are derived automatically from related child records

Answer: B — A parent-side field aggregating count, sum, min or max across detail records

B) A roll-up summary sits on the master side of a master-detail relationship and stores an aggregate of its detail records, optionally filtered, recalculating as children change. A) describes a cross-object copy, not an aggregate. C) A formula works within one record, which is the closest conceptual neighbour. D) Report subtotals are not stored and cannot drive rules. E) No such derived picklist exists.

Which feature controls which picklist values a user sees on a field?

1. The record type, which maps a subset of the value set to that record type
2. Sharing rules, which widen record access beyond the org-wide default
3. Field history tracking, which records the old and new values on change
4. A validation rule, which rejects the save after the value has been chosen

Answer: A — The record type, which maps a subset of the value set to that record type

A) Right. Each record type maps a subset of the field's value set, and the record types available to a user are set on their profile or permission set. B) Sharing decides which records are visible. C) History tracking is an audit feature. D) A validation rule can reject a value but cannot remove it from the list.

How does a user move between apps and their tabs in Lightning Experience?

1. Through reports, which open datasets but provide no cross-app navigation
2. Through the Setup menu only, which is reserved for administrative configuration
3. Through the App Launcher plus each app's configurable navigation bar of items
4. Through global search, which finds records but does not switch app context
5. Through the mobile app only, since desktop navigation is fixed for all users

Answer: C — Through the App Launcher plus each app's configurable navigation bar of items

C) The App Launcher lists the apps a user is entitled to, and each Lightning app carries its own navigation bar whose items the admin defines in App Manager and assigns by profile. A) Reports are a destination, not navigation. B) Setup is for configuration. D) Search jumps to records without changing the app. E) Navigation is configurable on desktop and mobile alike.

When does a validation rule stop a record from being saved?

1. When the rule's formula returns false, meaning the entered data passed checks
2. Only when the record owner lacks edit access to one of the referenced fields
3. When the rule's formula evaluates to true, which raises the configured error
4. Whenever a permission set grants the user access to the object being edited
5. Only after the record has saved and a scheduled evaluation reviews the data

Answer: C — When the rule's formula evaluates to true, which raises the configured error

C) A validation rule fires at save time and a true result means the error condition was met, so the save is blocked and the message is displayed. A) inverts the logic, which is the single most common mistake with these rules. B) describes field-level security, a different control. D) Permissions decide access, not data validity. E) Validation is synchronous and happens before the record is committed.

Which feature lets the admin show different page layouts to sales and service users for the same object?

1. Profile assignment alone, which maps exactly one layout per object per user
2. Validation rules that reject the fields the other team should not populate
3. Sharing rules, which expose a different set of records to each team's users
4. Record types, with layouts assigned per profile and record type together

Answer: D — Record types, with layouts assigned per profile and record type together

D) Right. Record types segment the object by business process, and layout assignment is made for each combination of profile and record type. A) Without record types a profile maps to a single layout for the object. B) Validation rules police data, not presentation. C) Sharing rules decide which records are visible, not how they are laid out.

How should an admin show a closed cases component on the Account page only when the account has five or more?

1. A custom component built by a developer that counts the closed cases
2. A validation rule that blocks the save until five cases are closed
3. A sharing rule that reveals the closed cases to the account's owner
4. A component visibility filter in App Builder on a field or a formula

Answer: D — A component visibility filter in App Builder on a field or a formula

D) Right. Component visibility filters in Lightning App Builder evaluate record fields, including a formula or roll-up holding the case count, and show or hide the component with no code. A) Custom development is unnecessary and outside the admin remit. B) Validation rules act on save. C) Sharing rules govern record access, not page composition.

Where does an admin create a custom object along with its fields and record types?

1. In Lightning App Builder, which assembles components onto the record page
2. In Schema Builder only, which must be used before any object can be saved
3. In Object Manager in Setup, which holds fields, layouts and record types
4. In the Data Import Wizard, which defines the object as the file is loaded

Answer: C — In Object Manager in Setup, which holds fields, layouts and record types

C) Right. Object Manager is the single place where an object's fields, relationships, page layouts, record types and validation rules are defined. A) App Builder arranges existing components and fields on a page but creates no schema. B) Schema Builder is an optional visual view of the same metadata. D) The import wizard loads records into objects that already exist. (This item replaced a stale question that quoted a per-edition custom object limit.)

Which statement is true about converting a lookup relationship into a master-detail relationship?

1. It is allowed once every child record has a value in the lookup field
2. It is never allowed; the field must be deleted and rebuilt from scratch
3. It is always allowed, whatever data currently sits in the lookup field
4. It requires deleting all child records before the conversion will save

Answer: A — It is allowed once every child record has a value in the lookup field

A) Right. Because a detail record cannot be orphaned, the platform blocks the conversion until no child row has an empty lookup value. B) The conversion is supported, and reverting is possible while no roll-ups exist. C) Null values stop it. D) The records are kept; only the null references need populating first.

Which statement is true about formula fields?

1. They are read-only and recalculated when the record is saved or viewed
2. They consume record storage in the same way as ordinary data fields do
3. Users with edit access can type over the calculated value on the record
4. They run their own database operations when the formula result changes

Answer: A — They are read-only and recalculated when the record is saved or viewed

A) Right. A formula field is derived at runtime from other fields, so it is always read-only and never edited directly. B) The value is calculated rather than stored as record data. C) There is no way to override the result on a record. D) Formula fields do not write data or invoke automation of their own.

An admin needs a list of recent opportunities on the Account page. What is the standard approach?

1. A custom component built by a developer to query recent opportunities
2. The standard related list component in App Builder, or the page layout
3. A sharing rule granting the account owner access to those opportunities
4. A validation rule that keeps each opportunity linked to its account

Answer: B — The standard related list component in App Builder, or the page layout

B) Right. Related lists are declarative: include the list on the page layout, or place the related list component on the Lightning record page and choose the relationship and columns. A) No code is needed. C) Sharing decides visibility, not placement. D) Validation rules enforce data entry rules.

Page layout?

Controls field display, sections, related lists, buttons on record detail page.

Contrast lookup and master-detail relationships on ownership, sharing and deletion.

In a master-detail relationship the detail record has no owner and no sharing of its own — it inherits the master's owner, sharing and security — and deleting the master cascade-deletes the details; the field is required on the detail. A lookup is loosely coupled: the child keeps its own owner and sharing, the field can be optional, and deleting the parent leaves the child (the lookup is cleared, or deletion can be blocked). A junction object joins two objects many-to-many using two master-detail relationships, the first created becoming the primary master.

Lightning app?

Modern app builder. Includes utility bar (footer with shortcuts).

Lightning App Builder?

Drag-and-drop tool for building custom Lightning pages.