Objects and Applications

Extending objects with relationships, record types and Schema Builder, and extending the user experience with Lightning apps, Dynamic Forms and console apps (19% of exam).

5 minutes 5 Questions

In the Salesforce Certified Platform Administrator II (Advanced Administrator) exam, the 'Objects and Applications' domain tests your ability to design and configure data models and app structures that meet complex business requirements. Objects are the foundation of the Salesforce data model. Stan…

Concepts covered
Standard Lightning Page Components and Visibility RulesLightning Console Apps, Split View and Utility BarRoll-Up Summary FieldsMaster-Detail RelationshipsSchema BuilderRelated Lists and Related List ConfigurationConverting Between Lookup and Master-DetailLookup Relationships and Lookup FiltersLightning App Builder Record PagesObject Creator from a SpreadsheetLightning Page Assignment by App, Record Type and ProfileLightning Apps in App ManagerRecord Types and Business ProcessesCross-Object Formula FieldsCompact Layouts and PathLightning Page Performance and the Analyze ButtonJunction Objects and Many-to-Many RelationshipsDynamic ActionsDynamic Forms
Test mode:
Start practice test

Admin II - Objects and Applications Example Questions

Test your knowledge of Objects and Applications

Question 1

In a roll-up summary field, which kind of child formula field is ineligible to be chosen as the field to aggregate?

Correct Answer: One that references TODAY() or another dynamic date function

A formula that references TODAY(), NOW(), or another dynamic date function is non-deterministic. Its value changes over time without the record being saved, so Salesforce cannot keep a stored roll-up total accurate and blocks such fields from being aggregated.
Using ISPICKVAL() does not make a formula ineligible, because the result changes only when the record is edited. A currency formula built from fields on the same record is deterministic and can be summarized. Nested IF logic across numeric child fields is still deterministic, so complexity alone does not disqualify it.
Key concept: roll-up summary fields cannot aggregate dynamic (non-deterministic) formula fields or cross-object formulas.

Question 2

At Cloud Kicks, opportunities have a lookup field to a custom Service Agreement object. Sales reps must be able to find and select only active agreements that belong to the opportunity's account. The search dialog itself must limit their choices, and they must not be able to change the restriction. Finance users, who share a dedicated profile, must be able to select any agreement. What should the administrator configure?

Correct Answer: Create a required lookup filter with OR logic that exempts the finance profile

A required lookup filter limits the lookup search dialog to agreements that are active and match the opportunity's account, and users cannot remove it. Adding OR logic with a criterion on the current user's profile exempts Finance, letting them select any agreement.
An optional lookup filter lets users remove the filter in the dialog, which breaks the requirement that reps cannot change the restriction. A validation rule only fires on save and does not limit choices in the search dialog. Private OWD with sharing controls record visibility broadly and cannot filter by the opportunity's account.
Key concept: required lookup filters with profile-based exemptions.

Question 3

Cloud Kicks is designing a new data model for custom Shipment and Shipment Item objects. Each item must always belong to one shipment, and items must be deleted when their shipment is deleted. Users who can edit a shipment must be able to edit its items. The Shipment record must also show the total weight of its items, updated automatically. Which design should the administrator build to meet every requirement?

Correct Answer: Add a master-detail field on Shipment Item and a SUM roll-up summary on Shipment

A master-detail field on Shipment Item makes Shipment the parent. Every item must have a shipment, items are cascade-deleted with their shipment, and items inherit sharing from the parent, so anyone who can edit a shipment can edit its items. Master-detail also allows a native SUM roll-up summary of item weight on Shipment that updates automatically.
A standard lookup with a roll-up fails because lookups don't support native roll-up summaries or inherited sharing. Placing the master-detail on Shipment reverses the parent-child relationship. A required lookup with a flow still lacks inherited edit access and needs custom automation for the total.
Key concept: master-detail relationships, controlled-by-parent sharing, and roll-up summary fields.

More Objects and Applications questions
565 questions (total)
Practice 100 questions
One session at a time, always new questions