Praxis Academy
Home › Platform Administrator II › Objects and Applications

Platform Administrator II practice questions: Objects and Applications

Objects and Applications is 19% of the Salesforce Certified Platform Administrator II exam. It covers data model, record types and Lightning pages. Try these 5 free questions, then open each answer to see why every option is right or wrong.

01

In a master-detail relationship, what happens to the related detail records when someone deletes the master record?

  1. The system blocks the delete until the admin manually removes every related detail record.
  2. The detail records are automatically moved to a default master record chosen by the admin.
  3. All related detail records are automatically cascade-deleted along with the master record, and both master and detail records are placed in the Recycle Bin.
  4. The detail records stay in the system as unrelated, orphaned records with a blank relationship field.
Show answer

Answer: C

A. The system blocks the delete until the admin manually removes every related detail record.Incorrect. The master delete is not blocked; the details are removed automatically through cascade delete.
B. The detail records are automatically moved to a default master record chosen by the admin.Incorrect. Master-detail has no concept of reparenting to a default master; cascade delete always applies.
C. All related detail records are automatically cascade-deleted along with the master record, and both master and detail records are placed in the Recycle Bin. ✓Correct. Deleting the master removes its details as well, and the whole set lands in the Recycle Bin and can be restored together.
D. The detail records stay in the system as unrelated, orphaned records with a blank relationship field.Incorrect. Orphaned details are possible with lookups, not master-detail, where cascade delete is mandatory.

Why: Master-detail relationships bind children tightly to their parent. Deleting the master cascade-deletes every detail record, and all of them go to the Recycle Bin, where restoring the master brings the details back too. Lookup relationships behave differently: the child survives with an empty parent field.

02

On the Account record page, a custom Lightning component should be shown in the Salesforce mobile app but hidden on desktop. Which Lightning App Builder feature controls component display by device?

  1. Build two Lightning Record Pages for Account, one for desktop and one for mobile, and place the custom component only on the mobile page.
  2. Add a field-level permission filter in Lightning App Builder that limits the component to users with the 'Salesforce Mobile App Access' permission.
  3. Edit the component's .js-meta.xml target definition so that it renders only on mobile.
  4. Add a Component Visibility Rule in Lightning App Builder with the filter 'Form Factor = Phone' so the component appears only on mobile devices.
Show answer

Answer: D

A. Build two Lightning Record Pages for Account, one for desktop and one for mobile, and place the custom component only on the mobile page.Incorrect. Separate pages would work but mean duplicating and maintaining two configurations; a form factor visibility rule is simpler.
B. Add a field-level permission filter in Lightning App Builder that limits the component to users with the 'Salesforce Mobile App Access' permission.Incorrect. No standard 'Salesforce Mobile App Access' permission exists for filtering component visibility.
C. Edit the component's .js-meta.xml target definition so that it renders only on mobile.Incorrect. Changing component metadata is a code change; the requirement is a configuration-level fix in Lightning App Builder.
D. Add a Component Visibility Rule in Lightning App Builder with the filter 'Form Factor = Phone' so the component appears only on mobile devices. ✓Correct. The 'Form Factor' filter restricts the component to a device type, so choosing 'Phone' makes it visible only on mobile.

Why: Component Visibility Rules include a Form Factor filter (Desktop, Phone, Tablet). Setting the rule to Form Factor = Phone shows the component only on mobile, with no second page and no code changes.

03

A validation rule that relies on ISCHANGED() is stopping an update the admin believes is valid. In a validation rule, what does ISCHANGED() evaluate to?

  1. ISCHANGED() exists only in Apex and cannot appear in declarative validation rules or workflow criteria.
  2. ISCHANGED() is TRUE only when a record is first created (insert) and does not work for updates.
  3. ISCHANGED() is TRUE when the field value differs from the value on any other record in the org with the same name, flagging duplicates across records.
  4. ISCHANGED() is TRUE when the field value being saved differs from the value stored at the last save, which makes it useful for catching edits during updates.
Show answer

Answer: D

A. ISCHANGED() exists only in Apex and cannot appear in declarative validation rules or workflow criteria.Incorrect. ISCHANGED() is a standard formula function usable in validation rules, legacy workflow criteria and other declarative tools.
B. ISCHANGED() is TRUE only when a record is first created (insert) and does not work for updates.Incorrect. It returns FALSE on insert because no earlier value exists; it is meant for updates.
C. ISCHANGED() is TRUE when the field value differs from the value on any other record in the org with the same name, flagging duplicates across records.Incorrect. It compares the field against its own prior value on the SAME record, never against other records.
D. ISCHANGED() is TRUE when the field value being saved differs from the value stored at the last save, which makes it useful for catching edits during updates. ✓Correct. It checks the new value against the last saved value: TRUE if it changed, FALSE if not, and always FALSE on insert.

Why: In a validation rule, ISCHANGED(field) is TRUE when the value being saved is different from the previously committed value (the same comparison as against PRIORVALUE(field)). On inserts it returns FALSE. A typical use is blocking certain edits, such as moving a stage backward.

04

On Opportunity, an admin creates a cross-object formula field whose formula is Account.Industry. Which limitation should the admin keep in mind?

  1. Formula fields cannot pull values from parent objects; only fields on the same object are allowed.
  2. Cross-object formulas can go up to 10 relationships deep, but their result is not live; it refreshes only when the child record is saved.
  3. When Account.Industry changes on the Account, the formula value on the Opportunity does not update until the Opportunity is saved again.
  4. Cross-object formula fields cannot serve as filter criteria in reports, flow entry conditions or other automation, since they are calculated when read rather than stored.
Show answer

Answer: D

A. Formula fields cannot pull values from parent objects; only fields on the same object are allowed.Incorrect. Cross-object formulas are supported and can reach parent fields up to 10 relationships away.
B. Cross-object formulas can go up to 10 relationships deep, but their result is not live; it refreshes only when the child record is saved.Incorrect. The formula is evaluated when read, so it reflects parent changes without saving the child.
C. When Account.Industry changes on the Account, the formula value on the Opportunity does not update until the Opportunity is saved again.Incorrect. The value reflects the current parent field; re-saving the Opportunity is not required.
D. Cross-object formula fields cannot serve as filter criteria in reports, flow entry conditions or other automation, since they are calculated when read rather than stored. ✓Correct (per source key). Because formula values are computed at read time instead of stored, they are not usable as filter criteria in these contexts.

Why: Formula fields are calculated when the record is read and are not stored in the database. The source treats this as preventing their use as filters in reports, flow entry conditions and SOQL WHERE clauses, and notes that cross-object formulas also cannot be indexed. When filtering on such values is required, a stored field maintained by automation is suggested.

05

Software licenses are stored as custom 'License__c' records linked to Account. If an Account is deleted, the License records must stay in the system for auditing, yet active Licenses should always point to an Account. Which relationship type and setup meets both needs?

  1. Master-Detail from License__c to Account; deleting the Account cascade-deletes the Licenses, which can be reviewed in the Recycle Bin before they are purged.
  2. A custom object with a Master-Detail to Account and a Lookup to an Archive object, moving License records to the Archive object before deletion.
  3. Master-Detail plus a before-delete Flow on Account that reparents every License to a default 'Archived Accounts' Account before the master is removed.
  4. A Lookup from License__c to Account using the 'Don't delete this field's value' option, so deleting the Account empties the Account field on the Licenses and keeps the License records.
Show answer

Answer: D

A. Master-Detail from License__c to Account; deleting the Account cascade-deletes the Licenses, which can be reviewed in the Recycle Bin before they are purged.Incorrect. Cascade delete removes the Licenses; the Recycle Bin is only temporary, and the requirement is permanent retention.
B. A custom object with a Master-Detail to Account and a Lookup to an Archive object, moving License records to the Archive object before deletion.Incorrect. Extra objects and moves over-engineer a need that a plain Lookup with clear-on-delete already meets.
C. Master-Detail plus a before-delete Flow on Account that reparents every License to a default 'Archived Accounts' Account before the master is removed.Incorrect. Reparenting through a Flow is possible but adds needless coupling; a Lookup is simpler.
D. A Lookup from License__c to Account using the 'Don't delete this field's value' option, so deleting the Account empties the Account field on the Licenses and keeps the License records. ✓Correct. Lookups do not cascade; with the clear-value behavior, deleting the Account nulls the field and keeps the License records.

Why: A Lookup is not tightly coupled like Master-Detail. When the Account is deleted, Salesforce can clear the lookup on related License records instead of deleting them, so every License survives for audit while the Account can still be removed.

Find out if you're ready to pass

Take the free Platform Administrator II diagnostic: 20 questions, no account needed. Then unlock all 180 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam