CRT-402 無料問題集「Salesforce Certification Preparation for Platform App Builder」

（A）External ID

（B）Salesforce Record ID

（C）TEXT(Id)

（D）CASESAFE(Id)

（A）Next Best Action

（B）In-App Guidance

（C）Path

（D）Flow

（A）Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record

（B）Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.

（C）Create a single account record, add each rep as a contact and create a custom dealer object

（D）Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

（A）Rich text field values of all lengths are displayed fully in reports.

（B）Field History Tracking records value changes of 255 characters or less.

（C）Audit Trail is available through REST API extracts.

（D）Data loss may occur when changing custom field types.

（A）Custom fields

（B）Custom actions

（C）Detail page layout

（D）System administrator profile

（E）Lightning App Builder

（A）One invocable process per object.

（B）One Workflow rule per object.

（C）One record change process perobject.

（D）One Flow per object.

（A）User will be able to edit the description field only.

（B）User will see the record is now owned by their manager.

（C）User will be presented with a 'Record Lock' notification.

（D）User will be able to edit the name, but unable to edit the description.

（A）Update the custom field's Field Level Security in setup to allow the agent read-only access to the field.

（B）Create a new profile to allow for read-only access to the field via Field Level Security and assign it to the agent

（C）Create a permission set that allows read-only access to the field via Field Level Security and assign it to the agent.

（D）Update the Customer Service Profile already assigned to the agent to allow for read-only access to the field via Field Level Security

（A）Next Best Action

（B）In-App Guidance

（C）Path

（D）Flow

（A）A field type change is included in the change set.

（B）Profiles are included in the change set.

（C）Dependentfields are included in the change set.

（D）Roles are included in the change set.

（A）Use Import Wizard to import the records.

（B）Use Data Loader to import the records.

（C）Include the currency ISO code in all currency fields in the import file.

（D）Include the currency ISO Code Column in the import file.

（E）Use import the currency ISO Code Column in the import file.

（A）AND( $UserRole.Name != 'Marketing',ISCHANGED(Retail_Opt_In__c),
ISPICKVAL(Retail_0pt_In_c,"Yes") )

（B）AND( $UserRole.Name != 'Marketing', Retail_Opt_In_c = "Yes" )

（C）AND( $UserRole.Name = 'Marketing', Retail_Opt_In__c= "Yes" )

（D）AND( $UserRole.Name = 'Marketing', ISPICKVAL(Retail_Opt_In_c,"Yes") )

（A）Scratch Org

（B）Partial Copy

（C）Developer

（D）Developer Pro

（A）Give the managerthe "API Enabled" permission to permit approval responses by email.

（B）Submit the record for approval from an automated process.

（C）Use a validation rule and an email alert to the manager requesting approval.

（D）Change the entry criteria on the approval process to criteria are met and lock the record on initial submission.

（A）Lookup field

（B）Number field

（C）Master-detail relationship field

（D）Roll-up summary field

（A）Apex

（B）Formula field

（C）Workflow

（D）Roll-up summary field

（A）Picklist dependency, page layouts, record types

（B）Custom button, validation rule, record types

（C）Process builder field update, quick action, record type

（D）Page layout, record types, process builder field update

（A）A custom detail page link on the Contract object

（B）Quick Action on the Contracts object

（C）A custom detail page link on the Account object

（D）Quick Action on the Account object

（A）The NOW() function in the formula field

（B）A cross-object workflow updating a field referenced by the formula field

（C）A cross-object field reference in the formula field

（D）The CASE() function in the formula field

（A）Activities

（B）Path

（C）Chatter

（D）Highlights panel