Praxis Academy
Home › Platform App Builder › Data Modeling and Management

Platform App Builder practice questions: Data Modeling and Management

Data Modeling and Management is 20% of the Salesforce Certified Platform App Builder exam. It covers relationships, field types, external IDs and data tools. Try these 21 free questions, then open each answer to see why every option is right or wrong.

01

A property management firm has two unrelated custom objects, Inspection__c and Building__c. About three inspections are logged per building each year. Deleting a building must automatically delete its inspections, and each inspection must use the same sharing and access as its building. How should the Platform App Builder relate the objects?

  1. Add a required lookup relationship field on Building__c that points to Inspection__c.
  2. Add a master-detail relationship field on Building__c that points to Inspection__c.
  3. Add a required lookup relationship field on Inspection__c that points to Building__c.
  4. Add a master-detail relationship field on Inspection__c that points to Building__c.
Show answer

Answer: D

A. Add a required lookup relationship field on Building__c that points to Inspection__c.Incorrect. The field sits on the wrong object, and lookups neither cascade delete nor pass down the parent's sharing.
B. Add a master-detail relationship field on Building__c that points to Inspection__c.Incorrect. This would make Building the child of Inspection, the reverse of what is needed.
C. Add a required lookup relationship field on Inspection__c that points to Building__c.Incorrect. The object is right, but a lookup does not cascade delete or inherit the parent's sharing.
D. Add a master-detail relationship field on Inspection__c that points to Building__c. ✓Correct. A master-detail field on the child Inspection__c deletes inspections with their building and makes them inherit its sharing.

Why: Both requirements, cascade delete and inherited sharing, are built-in behaviors of master-detail relationships. The relationship field is always created on the detail (child) object. Inspection is the 'many' side, so the master-detail field goes on Inspection__c and points to Building__c. Deleting a building then removes its inspections, and inspections follow the building's access. Reference: Object Relationships Overview

02

A Platform App Builder creates a master-detail relationship with Galaxy__c as the parent and Star__c as the child. What does this mean for users who want to report on Galaxy__c together with Star__c?

  1. A new custom report type must be built for Star__c using lookup fields from Galaxy__c.
  2. A Star__c report type that includes Galaxy__c as a field is created automatically.
  3. A Galaxy__c with Star__c report type is created automatically.
  4. A new custom report type must be built for Galaxy__c with Star__c.
Show answer

Answer: C

A. A new custom report type must be built for Star__c using lookup fields from Galaxy__c.Incorrect. No manual work is required; the parent-with-children report type is generated automatically.
B. A Star__c report type that includes Galaxy__c as a field is created automatically.Incorrect. The generated report type has the parent as primary (Galaxy with Star), not the child.
C. A Galaxy__c with Star__c report type is created automatically. ✓Correct. Salesforce automatically creates a 'Galaxy__c with Star__c' report type when both objects allow reports.
D. A new custom report type must be built for Galaxy__c with Star__c.Incorrect. The report type is created automatically, so no custom report type is needed.

Why: Creating a master-detail relationship has a reporting side effect. When both objects are enabled for reports, Salesforce automatically generates a standard 'parent with children' report type, here 'Galaxy__c with Star__c'. Users can report on galaxies with their related stars with no extra setup. Reference: Criteria to Generate a Standard Report Type

03

A computer services company has a custom service plan object, and each service plan must be linked to exactly one contact. The support manager found that when the wrong contact is linked, reps cannot change it. The Platform App Builder has confirmed the users have proper field access and that no validation rules exist on service plans. What is the cause?

  1. The Allow reparenting checkbox (Child records can be reparented to other parent records after they are created) is selected.
  2. The Read Only radio button (Allows users with at least Read access to the Master record to create, edit, or delete related Detail records) is chosen.
  3. The Read/Write radio button (Allows users with at least Read/Write access to the Master record to create, edit, or delete related Detail records) is chosen.
  4. The Allow reparenting checkbox (Child records can be reparented to other parent records after they are created) is cleared.
Show answer

Answer: D

A. The Allow reparenting checkbox (Child records can be reparented to other parent records after they are created) is selected.Incorrect. If reparenting were allowed, reps could change the contact.
B. The Read Only radio button (Allows users with at least Read access to the Master record to create, edit, or delete related Detail records) is chosen.Incorrect. This sharing setting controls who may create, edit or delete detail records, not whether the parent can change.
C. The Read/Write radio button (Allows users with at least Read/Write access to the Master record to create, edit, or delete related Detail records) is chosen.Incorrect. This sharing setting controls who may create, edit or delete detail records, not whether the parent can change.
D. The Allow reparenting checkbox (Child records can be reparented to other parent records after they are created) is cleared. ✓Correct. With Allow reparenting unchecked, the master record (the contact) cannot be changed once the detail record exists.

Why: Field access and validation rules are ruled out, so the block comes from the relationship itself. 'Allow reparenting' on a master-detail relationship decides whether a detail record's parent can be changed after creation. When it is unchecked, the Contact can be set once and never changed, which is exactly what the reps experience. Reference: Considerations for Object Relationships

04

Helix Labs exports opportunity data to Excel and must have the 18-character record ID so that no two records get confused. What formula should the Platform App Builder use for the new field?

  1. ISNUMBER(Id)
  2. CASESAFEID(Id)
  3. TEXT(Id)
  4. VALUE(Id)
Show answer

Answer: B

A. ISNUMBER(Id)Incorrect. ISNUMBER() only returns true or false and does not transform an Id.
B. CASESAFEID(Id) ✓Correct. CASESAFEID() produces the 18-character, case-insensitive version of the record Id.
C. TEXT(Id)Incorrect. TEXT() does not append the three extra checksum characters.
D. VALUE(Id)Incorrect. VALUE() turns text into a number and would error on an Id.

Why: Salesforce displays 15-character IDs that are case-sensitive. Excel ignores letter case, so two IDs that differ only in capitalization can look like the same value after export. CASESAFEID() turns the 15-character ID into its 18-character, case-insensitive form, which stays unique in any tool. Reference: CASESAFEID

05

Helix Labs wants to store the content of a product white paper in a field on the Product object. The content includes tables, lists and images. Which field type should the Platform App Builder choose so it displays correctly?

  1. Text Area
  2. Text Area (Long)
  3. Text Area (Rich)
  4. Text Area (Encrypted)
Show answer

Answer: C

A. Text AreaIncorrect. A Text Area stores a short amount of plain text with no formatting or images.
B. Text Area (Long)Incorrect. A Long Text Area allows more characters but still holds plain text only.
C. Text Area (Rich) ✓Correct. A Rich Text Area supports formatting, lists, tables and images via its toolbar.
D. Text Area (Encrypted)Incorrect. An encrypted text field masks sensitive values and is plain text only.

Why: Only a Rich Text Area field handles formatted content such as bold text, lists, tables and embedded images. It includes an editor toolbar for formatting and inserting images, so the white paper keeps its structure. Reference: Custom Field Types

06

Helix Labs has found a second sun and now wants the Sun__c to Planet__c relationship to be a lookup instead of master-detail. Before the change, what reporting impact should the Platform App Builder keep in mind?

  1. Existing reports built on the Salesforce-created Sun__c with Planet__c report type will be deleted.
  2. Existing roll-up summary fields will stay on Sun__c and remain reportable, but will stop updating.
  3. Existing roll-up summary fields will be removed from Sun__c and from every report that uses them.
  4. Existing reports built on the Salesforce-created Sun__c with Planet__c report type may become unusable but will not be deleted.
Show answer

Answer: C

A. Existing reports built on the Salesforce-created Sun__c with Planet__c report type will be deleted.Incorrect. The report type and its reports remain; only the roll-up summary fields go away.
B. Existing roll-up summary fields will stay on Sun__c and remain reportable, but will stop updating.Incorrect. Roll-up summary fields cannot exist on a lookup, so they do not stay on the object.
C. Existing roll-up summary fields will be removed from Sun__c and from every report that uses them. ✓Correct. Roll-ups need master-detail, so moving to a lookup removes them from the object and from reports. (In practice, Salesforce makes you delete them before it allows the conversion.)
D. Existing reports built on the Salesforce-created Sun__c with Planet__c report type may become unusable but will not be deleted.Incorrect. The report type and reports stay usable; the roll-up fields are what is affected.

Why: Roll-up summary fields depend on a master-detail relationship; a lookup cannot support them. Converting the relationship therefore means losing the roll-up summary fields, and because the fields no longer exist, they also disappear from reports that included them. The report type and reports themselves remain. Reference: Roll-Up Summary Field

07

Helix Labs has a Country picklist on three different custom objects. The values must stay identical across all three objects. Which feature should the Platform App Builder use?

  1. State and Country Picklist
  2. Next Best Action
  3. Field Update
  4. Global Picklist Value Set
Show answer

Answer: D

A. State and Country PicklistIncorrect. State and Country picklists apply to standard address fields, not to custom picklists.
B. Next Best ActionIncorrect. Next Best Action suggests actions to users; it does not manage picklist values.
C. Field UpdateIncorrect. A field update changes data in automation; it does not keep value lists aligned.
D. Global Picklist Value Set ✓Correct. A Global Value Set provides one value list shared by picklists on multiple objects.

Why: A Global Value Set is a reusable list of picklist values defined once, independently of any object. Picklist fields on several objects can be based on it, and editing the set updates every field that uses it. Reference: Create a Global Picklist Value Set

08

Helix Labs will use a custom object to record installation details after a container is bought. Sales reps must be able to see every installation linked to their opportunities. What relationship should the new object have with Opportunity?

  1. Lookup
  2. Many to Many
  3. Master-Detail
  4. Hierarchical
Show answer

Answer: A

A. Lookup ✓Correct. A lookup from the installation object to Opportunity shows related installations on the opportunity without master-detail features.
B. Many to ManyIncorrect. Many-to-many requires a junction object, which the scenario does not need.
C. Master-DetailIncorrect. Master-detail brings cascade delete and inherited sharing that are not required.
D. HierarchicalIncorrect. Hierarchical relationships are available only on the User object.

Why: A lookup from the installation object to Opportunity links the records and makes an installations related list available on the opportunity. The scenario needs no cascade delete, roll-ups or inherited sharing, so master-detail would add unnecessary complexity. Reference: Object Relationships Overview

09

Helix Labs wants the Account detail page to show how many Closed Won opportunities have a close date in the past year. What should the Platform App Builder use?

  1. Roll-up summary field
  2. Validation rule
  3. Formula field
  4. Activity timeline
Show answer

Answer: A

A. Roll-up summary field ✓Correct. A COUNT roll-up on Account filtered to Closed Won displays the number on the account page. Roll-up filters cannot use relative dates such as 'last year', so a helper field (for example, a checkbox kept current by a flow) is typically used for the date window.
B. Validation ruleIncorrect. Validation rules prevent saves; they cannot display counts.
C. Formula fieldIncorrect. A formula field cannot count related child records.
D. Activity timelineIncorrect. The Activity Timeline lists activities, not opportunity counts.

Why: A roll-up summary field with COUNT and filter criteria is the declarative way to show an aggregated count of child opportunities on the parent Account. It recalculates automatically as opportunities change and appears on the Account page without code. Reference: Create a Roll-Up Summary Field

10

Brightline Energy sets the Organization-Wide Default for Account to Private. Marketing owns some accounts but also needs to view accounts owned by sales. Sales and marketing sit in entirely separate branches of the role hierarchy. What feature lets marketing see the accounts owned by sales?

  1. Sharing rules
  2. Public groups
  3. Aliases
  4. Assignment rules
Show answer

Answer: A

A. Sharing rules ✓Correct. A sharing rule can extend sales-owned accounts to marketing even across separate hierarchy branches.
B. Public groupsIncorrect. A public group can be the target of a sharing rule, but a group alone grants no access.
C. AliasesIncorrect. Aliases are short user display names unrelated to sharing.
D. Assignment rulesIncorrect. Assignment rules route leads and cases; they do not share accounts.

Why: With a Private OWD, users see only their own records plus those granted by the hierarchy, sharing rules or manual sharing. Because the two teams are in different branches, the hierarchy grants marketing nothing. A sharing rule can open sales-owned accounts to marketing based on roles, public groups or criteria. Reference: Sharing Rules | Salesforce Help

11

Brightline Energy has a custom service plan object, and each service plan must belong to exactly one contact. The support manager found that when a plan is linked to the wrong contact, reps cannot change it. The app builder has verified that users have proper field access and that no validation rules exist on service plans. What is the likely cause?

  1. The Read Only radio button, Allows users with at least Read access to the Master record to create, edit, or delete related Detail records, is selected.
  2. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.
  3. The Read/Write radio button, Allows users with at least Read/Write access to the Master record to create, edit, or delete related Detail records, is selected.
  4. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is checked.
Show answer

Answer: B

A. The Read Only radio button, Allows users with at least Read access to the Master record to create, edit, or delete related Detail records, is selected.Incorrect. This sharing option governs who can create, edit or delete detail records, not reparenting.
B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked. ✓Correct. When Allow reparenting is unchecked, a service plan's contact cannot be changed after creation.
C. The Read/Write radio button, Allows users with at least Read/Write access to the Master record to create, edit, or delete related Detail records, is selected.Incorrect. This sharing option governs who can create, edit or delete detail records, not reparenting.
D. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is checked.Incorrect. If reparenting were allowed, reps would be able to change the contact.

Why: The service plan is tied to its contact through a master-detail relationship. With field access and validation ruled out, the remaining cause is the relationship's 'Allow reparenting' setting, which is unchecked by default. While it is unchecked, the master (contact) on an existing detail record (service plan) cannot be changed. Reference: Considerations for Object Relationships | Salesforce Help

12

An energy company needs each Account to show how many Opportunity records are related to it. What should be used?

  1. Formula field
  2. An AppExchange solution
  3. Lookup field
  4. Roll-up summary field
Show answer

Answer: D

A. Formula fieldIncorrect. A formula field cannot count related child records.
B. An AppExchange solutionIncorrect. No AppExchange product is needed; this is a native feature.
C. Lookup fieldIncorrect. A lookup field defines a relationship but does not count anything.
D. Roll-up summary field ✓Correct. A roll-up summary field on Account with the COUNT type totals the related opportunities.

Why: The goal is a single number on the Account: a count of its child Opportunities. Account and Opportunity have a special relationship that behaves like master-detail, so a roll-up summary field can be created on Account. With the summary type set to COUNT, it tallies the related Opportunity records automatically, with no code or third-party product.

13

A utility company wants better case management. Cases must not be moved back to an earlier status, and certain fields must be mandatory when specific case conditions apply. What should the app builder implement?

  1. Set up validation rules with help text.
  2. Build dependent picklist fields and mark them required.
  3. Use an approval process to verify the field criteria.
  4. Mark the fields required on the page layout.
Show answer

Answer: A

A. Set up validation rules with help text. ✓Correct. Validation rules can block backward status changes and require fields under specific conditions, with a clear error message.
B. Build dependent picklist fields and mark them required.Incorrect. Dependent picklists filter values but cannot stop a status from being reverted.
C. Use an approval process to verify the field criteria.Incorrect. Approval processes route records for sign-off; they do not enforce data rules on save.
D. Mark the fields required on the page layout.Incorrect. Page-layout requirements apply in every situation, not only when certain criteria are met.

Why: Both requirements are conditional checks at save time. Validation rules can use PRIORVALUE() or ISCHANGED() to stop a status from moving backward, and logic such as AND(ISPICKVAL(Status, "Closed"), ISBLANK(Resolution_Notes__c)) to require fields only in certain situations. Their error messages tell users how to fix the record. A page-layout requirement applies all the time and cannot express either condition.

14

An app builder is adding a new field to a custom object and does not want it to appear on the custom report types that already exist. What should be done in the custom field setup?

  1. Take the new field off all page layouts.
  2. Remove its visibility for all report profiles.
  3. Give all report profiles read-only access.
  4. Uncheck auto add to custom report type.
Show answer

Answer: D

A. Take the new field off all page layouts.Incorrect. Page layouts do not determine which fields are in report types.
B. Remove its visibility for all report profiles.Incorrect. Hiding the field removes it from users entirely, which is not what was asked.
C. Give all report profiles read-only access.Incorrect. A read-only field can still appear in report types.
D. Uncheck auto add to custom report type. ✓Correct. Clearing 'Auto add to custom report type' during field creation keeps the field off existing custom report types.

Why: The field creation wizard has its own 'Auto Add to Custom Report Type' checkbox. When left selected, the new field is added to existing custom report types automatically; clearing it keeps the field out. Page layouts and field visibility are separate settings and do not control report type columns.

15

A biotech firm has a new custom Invoice object with an Invoice Number field. Before go-live, invoices will be migrated from an external system and must keep their existing Invoice Numbers. After the migration, every Invoice created in Salesforce must have a unique Invoice Number. How should the Platform App Builder set up the Invoice Number field?

  1. Use an AutoNumber field and migrate the invoices in Invoice Number order.
  2. Use a Text field and mark it as a unique External ID.
  3. Use a Text field for the original Invoice Number and an AutoNumber field for the Salesforce Invoice Number.
  4. Use a Text field and switch it to AutoNumber after the migration.
Show answer

Answer: B

A. Use an AutoNumber field and migrate the invoices in Invoice Number order.Incorrect. AutoNumber fields cannot be loaded with the existing invoice numbers.
B. Use a Text field and mark it as a unique External ID. ✓Correct. A unique External ID Text field keeps the original numbers, supports upserts, and enforces uniqueness from then on.
C. Use a Text field for the original Invoice Number and an AutoNumber field for the Salesforce Invoice Number.Incorrect. Two invoice number fields cause confusion and do not enforce uniqueness on the original numbers.
D. Use a Text field and switch it to AutoNumber after the migration.Incorrect. Converting to AutoNumber replaces the migrated values with new numbers.

Why: A Text field can store the original invoice numbers exactly as they are, which an AutoNumber field cannot accept during a load. Marking it as an External ID allows matching and upserting against the source system, and marking it Unique makes Salesforce reject duplicate numbers on every later save.

16

A solar installation company needs to relate the standard Contact object to a custom Solar Project object. One contact may be involved in many solar projects, and one solar project may involve many contacts. How should the app builder design the data model?

  1. Two master-detail relationships on a new custom object
  2. A master-detail relationship on Contact and another master-detail relationship on Solar Project
  3. Two lookup relationships on a new custom object
  4. A lookup relationship on Contact and another lookup relationship on Solar Project
Show answer

Answer: A

A. Two master-detail relationships on a new custom object ✓Correct. A junction object with one master-detail to Contact and one to Solar Project is the standard many-to-many model.
B. A master-detail relationship on Contact and another master-detail relationship on Solar ProjectIncorrect. A relationship field placed directly on Contact or Solar Project points to only one record on the other side.
C. Two lookup relationships on a new custom objectIncorrect. Two lookups can link the objects, but they lack the cascade delete and sharing inheritance a true junction object provides.
D. A lookup relationship on Contact and another lookup relationship on Solar ProjectIncorrect. Lookups on each object only create one-to-many links, not many-to-many.

Why: This is a many-to-many relationship: either side can have many related records on the other. A single relationship field on either object can only point to one record, so it cannot model this. The standard solution is a junction object in the middle with two master-detail relationships, one to Contact and one to Solar Project, so any contact can link to any number of projects and vice versa.

17

An astronomy education company wants the Type field from the parent Galaxy object shown on the child Star record. The app builder gets the error 'Picklist values are only supported in certain functions.' Which formula should the app builder use?

  1. TEXT(Galaxy__r.Type__c)
  2. ISPICKVAL(Galaxy__r.Type__c)
  3. VALUE(Galaxy__r.Type__c)
  4. String(Galaxy__r.Type__c)
Show answer

Answer: A

A. TEXT(Galaxy__r.Type__c) ✓Correct. TEXT() converts the parent's picklist value into text that the formula can return.
B. ISPICKVAL(Galaxy__r.Type__c)Incorrect. ISPICKVAL() tests a picklist against a specific value and returns true or false.
C. VALUE(Galaxy__r.Type__c)Incorrect. VALUE() turns text into a number; it does not convert picklists.
D. String(Galaxy__r.Type__c)Incorrect. String() is not a Salesforce formula function.

Why: A picklist field cannot be used as-is in most formula functions; it must first be converted to text. Wrapping the cross-object reference in TEXT() turns the parent's selected Type value into a string that the formula can display on Star.

18

A distributor has five years of sales history and wants to record the date of each customer's first purchase. How should the app builder use a roll-up summary for this?

  1. Add a new date field named First Order Date, then build a roll-up summary of type MIN to update it.
  2. Add a new roll-up summary field named First Order Date that uses type MIN on Opportunity Close Date, filtered to isWon = TRUE.
  3. Add a new date field named First Order Date, then fill it with a roll-up summary on Opportunity Close Date.
  4. Add a new roll-up summary field named First Order Date that uses type SUM on Opportunity Close Date.
Show answer

Answer: B

A. Add a new date field named First Order Date, then build a roll-up summary of type MIN to update it.Incorrect. The roll-up summary field holds the value itself; no separate date field is needed.
B. Add a new roll-up summary field named First Order Date that uses type MIN on Opportunity Close Date, filtered to isWon = TRUE. ✓Correct. MIN on Close Date, filtered to IsWon = TRUE, returns the earliest won opportunity date.
C. Add a new date field named First Order Date, then fill it with a roll-up summary on Opportunity Close Date.Incorrect. A roll-up summary does not 'set' a separate date field.
D. Add a new roll-up summary field named First Order Date that uses type SUM on Opportunity Close Date.Incorrect. SUM is not available for date fields.

Why: The first order date is the earliest Close Date among the account's won opportunities. MIN returns the smallest value across child records, while SUM cannot be used on dates. The roll-up summary field itself stores the result, and a filter of IsWon = TRUE limits it to deals that became real sales.

19

An app builder wants a formula field on Account that uses data from related Contacts, but the relationship does not appear in the formula editor. Which formula limitation explains this?

  1. The formula exceeds 5,000 characters.
  2. Contact and Account do NOT have a Master-Detail relationship.
  3. Child records cannot be referenced.
  4. The Account object has reached its formula field limit.
Show answer

Answer: C

A. The formula exceeds 5,000 characters.Incorrect. Formula length has nothing to do with the relationship being missing.
B. Contact and Account do NOT have a Master-Detail relationship.Incorrect. The relationship type is not the cause; formulas cannot reach child records over any relationship.
C. Child records cannot be referenced. ✓Correct. Cross-object formulas can reference parent records only, never child records such as an account's contacts.
D. The Account object has reached its formula field limit.Incorrect. Hitting the field limit would prevent creating the field, not hide the relationship.

Why: Cross-object formulas only travel upward, from a child to its parent. An Account can have many Contacts with different values, so there is no single child value to pull down into a formula. That is why the Contact relationship is not offered in the editor.

20

At a solar-equipment distributor, a custom object Galaxy__c is linked to a custom object Star__c through a lookup relationship. The app builder wants a roll-up summary field that shows how many Star__c records belong to each Galaxy__c record. What does the existing setup mean for meeting this goal?

  1. A formula field on the Galaxy__c object can deliver the roll-up result.
  2. Before any roll-up summary field can be built, the lookup must be changed to a master-detail relationship.
  3. A formula field on the Star__c object can deliver the roll-up result.
  4. Build a roll-up summary field on Galaxy__c whose field filter includes every related Star__c record.
Show answer

Answer: B

A. A formula field on the Galaxy__c object can deliver the roll-up result.Incorrect. A formula on the parent cannot count its child records.
B. Before any roll-up summary field can be built, the lookup must be changed to a master-detail relationship. ✓Correct. Roll-up summaries need master-detail, so the lookup has to be converted first; every Star__c record must reference a Galaxy__c.
C. A formula field on the Star__c object can deliver the roll-up result.Incorrect. A formula on the child cannot count its sibling records.
D. Build a roll-up summary field on Galaxy__c whose field filter includes every related Star__c record.Incorrect. Filters don't help; roll-up summary fields are simply unavailable on a lookup relationship.

Why: Roll-up summary fields exist only on the master side of a master-detail relationship. Because Galaxy__c and Star__c are joined by a lookup, no roll-up summary can be created, whatever formula or filter is used. Converting the lookup to master-detail (which requires every Star__c record to have a Galaxy__c value) unlocks a COUNT roll-up on Galaxy__c.

21

A service manager asks the Platform App Builder to color-code open cases by age: - Brand-new cases show a green circle. - Cases one day old show a yellow circle. - Cases three days old show a red circle. Which tool should the app builder use?

  1. Custom button
  2. Lightning web component
  3. Formula field
  4. Quick action
Show answer

Answer: C

A. Custom buttonIncorrect. A button needs a user click and shows no automatic indicator.
B. Lightning web componentIncorrect. A custom LWC means writing code when a formula field handles this declaratively.
C. Formula field ✓Correct. A formula using IMAGE() and IF logic on the case age displays the right colored circle automatically.
D. Quick actionIncorrect. A quick action depends on user interaction and doesn't display an indicator.

Why: A formula field can calculate the case age (for example TODAY() - DATEVALUE(CreatedDate)) and use nested IF logic with the IMAGE() function to return a green, yellow or red circle. It is declarative, needs no code and recalculates automatically.

Find out if you're ready to pass

Take the free Platform App Builder diagnostic: 20 questions, no account needed. Then unlock all 241 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam