CRT-403 Practice Questions

The app builder should validate the inbound change set to ensure a smooth deployment to

production. Validating an inbound change set allows the app builder to test whether the change set

can be deployed without errors in the target org. Validating an inbound change set does not affect

any data or metadata in the target org.

It will fail if there is a feature only available in the next version. According to the Salesforce

documentation, “If your sandbox is on a newer version than your production org, you can’t deploy

any components that are new in the sandbox version.” The change set components will not be

upgraded to the next version in production, the change set will not be automatically deployed when

production is upgraded, and the deployment is possible if there are no new features involved.

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

The best feature to use to ensure consistent case priority entry is Path. Path allows users to see key

fields and guidance for each stage of a process, such as a case lifecycle. Path can also enforce data

quality by making certain fields required at each stage. See [this article] for more information on

Path.

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

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.

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

Schema Builder is a tool that allows app builders to view and modify the data model of their

Salesforce org. Some of the capabilities of Schema Builder are:

Creating and editing custom objects and fields

Creating and editing relationships between objects

Showing selected objects on a page

Editing custom settings

Schema Builder cannot be used to create a new record type or view page layouts in a new window.

The correct validation rule formula to ensure that the Scheduled Ship Date field is properly filled out

before setting the Opportunity to Closed Won is:

OR(ISPICKVAL( StageName ,“Closed Won”) && (

Scheduled_Ship_Date_cCloseDate)>14,ISBLANK(Scheduled_Ship_Date_c))

This formula checks two conditions: if the StageName is Closed Won and the Scheduled Ship Date is

more than 14 days after the Close Date, or if the Scheduled Ship Date is blank. If either condition is

true, the validation rule will fire and prevent saving the record. The other formulas are incorrect

because they either use incorrect syntax (such as “=” instead of “,” or missing parentheses) or

incorrect logic (such as checking if the Scheduled Ship Date is less than 14 days after the Close Date)

An indirect lookup relationship is a custom relationship between two objects that are linked by an

external ID field. The external ID field must be a custom field on the parent object that has the

“External ID” attribute enabled. The child object must be a standard or custom object that is on the

detail side of a master-detail or lookup relationship.

The most likely reason why users are unable to view the custom Lightning component on mobile

devices is that the component has been developed for Desktop Pages only. Some components are

not supported on mobile devices or have different behavior on mobile devices. An app builder

should check the component documentation or metadata to see if it is compatible with mobile

devices.