Free CRT-403 Exam Braindumps
Prepare for your Platform App Builder Certification Questions 86–90 (page: 19)

Updated On: 10-Feb-2026

Ursa Major Solar wants to convert the relationship between Galaxy and Star from a lookup relationship to a master-detail relationship so each Galaxy record can be equipped with a roll-up summary count of Star records.
Which two considerations should be made?
Choose 2 answers

  1. The Star records are all required to have an existing value in their Galaxy field.
  2. The Galaxy object has fewer than two existing master-detail relationships.
  3. The Galaxy object is required to contain existing roll-up summary fields.
  4. The Star object has fewer than two existing master-detail relationships.

Answer(s): A,B

Explanation:

The two considerations that should be made are: The Star records are all required to have an existing value in their Galaxy field. This is a prerequisite for converting a lookup relationship to a master- detail relationship. A lookup relationship is an optional relationship that links two objects together, but does not enforce referential integrity or cascade delete. A master-detail relationship is a required relationship that links two objects together and enforces referential integrity and cascade delete. To convert a lookup relationship to a master-detail relationship, all child records must have a value in their lookup field that references an existing parent record. The Galaxy object has fewer than two existing master-detail relationships. This is another prerequisite for converting a lookup relationship to a master-detail relationship. An object can have up to two master-detail relationships with other objects and can act as both the parent and child in different relationships. To convert a lookup relationship to a master-detail relationship, the parent object must have fewer than two existing master-detail relationships with other objects. The Galaxy object is required to contain existing roll- up summary fields is not a valid consideration, as it is not related to converting a lookup relationship to a master-detail relationship.



Universal Containers has two types of applicants, hourly and salary. There are separate record types for each.
While all members of the human resource department need to be able to view all applicant records, only the hiring Manager and VP of HR should be able to create salary applicant records.
What should the app builder recommend to meet this requirement?

  1. Update the org-wide default to private and create a sharing rule for the role of recruiting manager.
  2. Create a permission set containing the salary record type and assign it to the appropriate users.
  3. Remove "create" permission for the salary applicant object for everyone except the manager and VP.
  4. Configure the hourly record type as the default and instruct non-management users to accept the default record type.

Answer(s): B

Explanation:

A permission set containing the salary record type and assigning it to the appropriate users would allow only those users to create salary applicant records, while still allowing all users to view all applicant records. This is the most granular and flexible way to meet the requirement



The DreamHouse Realty (DR) service manager has asked for some improvements in case management to enforce process compliance so that cases are unable to be reverted to an earlier case status, and to ensure that certain fields are required when specific case criteria are met.
What solution should an app builder implement to meet these requirements?

  1. Workflow Rules
  2. Process Builder
  3. A Validation Rules
  4. Activities Component

Answer(s): C

Explanation:

A validation rule can enforce process compliance by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can prevent users from reverting to an earlier case status or leaving certain fields blank when specific case criteria are met



Cloud Kicks (CK) wants to track orders against inventory, ensuring its ability to fulfill order requests. CK created a junction object called Request Inventory to enable many-to-many relationships with the

Inventory and Order objects.
What does the app builder need to provide to ensure users can view Request Inventory records?

  1. Read access to both master objects.
  2. Apex-based sharing on the first master object.
  3. Sharing rules on Request Inventory object.
  4. Read access to the first master object.

Answer(s): A

Explanation:

To view a junction object record, a user must have at least read access to both master objects. This is because the junction object inherits the sharing and security settings from both master objects



An app builder would like to streamline the user experience by reflecting summarized calculations of specific fields on various objects.
Which field types could be used in roll-up summary fields to accomplish this? Choose 3 answers

  1. Currency
  2. Percent
  3. Date
  4. Checkbox
  5. Time

Answer(s): A,B,D

Explanation:

Roll-up summary fields can only be created on master-detail relationships, and they can only calculate numeric fields, such as currency, percent, and number. Date and time fields are not supported for roll-up summary fields. Checkbox fields can be used in roll-up summary filters, but not in the field to aggregate



Viewing page 19 of 60
Viewing questions 91 - 95 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!