support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Salesforce
  4. CRT-403

Salesforce CRT-403 Exam Prep
Prepare for your Platform App Builder Certification (Page 7 )

Updated On: 28-Aug-2026
Page 7 of 60
PDF with 291 Questions

Universal Containers created a custom object called Component to capture details about products sold.
What approach should an app builder take to show Component as a related list on Product?

  1. Create a master-detail relationship on Product to Component. Add the Component related list to the Product page layout.
  2. Create a junction object to relate Component and Product. Add the Component related list to the Product page layout.
  3. Create a roll-up on Product. Add the Component related list to the Product page layout.
  4. Create a lookup relationship on Component to Product. Add the Component related list to the Product page layout.

Answer(s): D

Explanation:

To show Component as a related list on Product, a lookup relationship on Component to Product should be created. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. A lookup relationship also allows users to add the related list of the child object to the parent object's page layout.



What are the limitations of Schema Builder when creating a custom object?

  1. "Save" should be clicked each time a new object, field, or relationship is created.
  2. Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas.
  3. Relationships can be made to any custom objects, but any relationships to standard objects should be built in Lightning Object Manager.
  4. Custom fields can be added to any custom objects, excluding formula field types.

Answer(s): B

Explanation:

It lacks setting up field-level security and adding fields to the page layout, so you have to choose the manual way of field creation. Adds another layer of risk with changes in Schema Builder since it is deployed in real-time.

Salesforce Schema Builder is a powerful tool for visualizing and creating objects, fields, and relationships in Salesforce, but it has certain limitations when building custom objects. Option B (Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas): In Schema Builder, while you can create new custom objects, fields, and relationships, you cannot directly add fields to the page layout from within the Schema Builder interface. After creating a field, you need to navigate to the Page Layout Editor to manually place the new field on the layout.


Reference:

Schema Builder Overview
Option A: This is incorrect because you can perform multiple actions within Schema Builder without needing to click Save each time. Salesforce will save these changes when you click Save once at the end.
Option C: While relationships can be created in Schema Builder for both standard and custom objects, there is no requirement to use Lightning Object Manager to create relationships with standard objects.
Option D: Schema Builder supports the creation of formula fields along with other types of fields.
There is no exclusion for formula fields.
In summary, Option B is the correct limitation of Schema Builder: you cannot add fields to page layouts directly from the Schema Builder interface.


Schema Builder Limitations



Cloud Kicks received a new requirement to calculate summaries from child objects of a standard object. The team would prefer to solve this declaratively.
What are two considerations an app builder should evaluate? Choose 2 answers

  1. An app builder is unable to change a look up to a master-detail relationship.
  2. An object can have up to two master-detail relationships.
  3. A trigger on save or update can kick off calculations.
  4. A value is required in all records of the lookup field prior to converting to a master-detail relationship.

Answer(s): B,D

Explanation:

When Cloud Kicks needs to calculate summaries from child objects of a standard object declaratively, a few key considerations about master-detail relationships come into play. Master-detail relationships are critical in Salesforce when working with roll-up summary fields, which allow you to calculate values from child records.
Option B: An object can have up to two master-detail relationships. Salesforce allows an object to have two master-detail relationships. This is important because if you want to aggregate child record data using roll-up summary fields, you need to have a master-detail relationship in place. Each master-detail relationship links a child object to a parent, and you can create roll-up summary fields on the parent object to summarize the child record data.


Reference:

Master-Detail Relationship Overview
Option D: A value is required in all records of the lookup field prior to converting to a master-detail relationship.
One important consideration when converting a lookup relationship into a master-detail relationship is that the lookup field must contain values for all existing child records. This is because master-detail relationships have tighter coupling between parent and child records, and a child cannot exist without a parent in a master-detail scenario. Thus, the field cannot be null during the conversion process.


Convert a Lookup Relationship to a Master-Detail Relationship Option A: An app builder can convert a lookup relationship to a master-detail relationship if the above condition (that all lookup fields are populated) is met, so this option is incorrect. Option C: Triggers are part of custom development using Apex, and the question specifies the solution should be declarative. Therefore, triggers would not be a relevant declarative tool for this scenario.



An app builder is creating a Lightning record page and has added Mobile & Lightning Actions to the page layout.
What two components could be included on the layout to display the actions? Choose 2 answers

  1. Highlights panel
  2. Chatter
  3. Activities
  4. Path

Answer(s): A,C

Explanation:

To display the actions on the Lightning record page, two components could be included on the layout:
Highlights panel: The highlights panel displays key information and actions for a record based on the compact layout. Users can see and perform actions such as edit, clone, delete, follow, etc. from the highlights panel. [Source]

Activities: The activities component displays tasks and events related to a record. Users can also create new tasks and events, log calls, send emails, and view past activities from this component.



A Cloud Kicks employee submitted an opportunity for approval by their manager.
What would happen if the employee attempts to edit the description field after submission?

  1. User will be presented with a 'Record Lock' notification.
  2. User will be able to edit the description field only.
  3. User will see the record is now owned by their manager.
  4. User will be able to edit the name, but unable to edit the description.

Answer(s): A

Explanation:

If an employee attempts to edit the description field after submitting an opportunity for approval, they will be presented with a `Record Lock' notification. This means that the record is locked for editing while it is in the approval process and only users with the "Modify All" permission or users above them in the role hierarchy can edit it. [Source]



  PDF
Viewing page 7 of 60
Viewing questions 31 - 35 out of 291 questions


Post your Comments and Discuss Salesforce CRT-403 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!