Free CRT-403 Exam Braindumps
Prepare for your Platform App Builder Certification Questions 101–105 (page: 22)

Updated On: 10-Feb-2026

universal containers is migrating its sales operations from a legacy system that was used. opportunities need to be imported with the proper country currency.
Which two steps should an app builder configure to meet these requirements?
Choose 2 answers.

  1. Include the currency ISO code in all currency fields in the import file.
  2. Use Data Loader to import the records.
  3. Include the currency ISO Code Column in the import file.
  4. Use import the currency ISO Code Column in the import file.
  5. Use Import Wizard to import the records.

Answer(s): A,B

Explanation:

To import opportunities with the proper country currency, the app builder needs to include the currency ISO code in all currency fields in the import file, and use Data Loader to import the records. Data Loader supports importing multiple currencies, while Import Wizard does not. The currency ISO code column in the import file specifies the currency for each record



An app builder wants to create a formula field on an Account to include data from related Contacts but is unable to find the relationship in the formula editor.
What is a limitation of formulas that could be causing the issue?

  1. Unable to reference the child records.
  2. A master-detail relationship should be created.
  3. Formula field limit reached on the Account object.
  4. More than 5,000 characters in the formula.

Answer(s): A

Explanation:

The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.
Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.


Reference:

Formula Field Considerations
Option B (A master-detail relationship should be created): While master-detail relationships allow for roll-up summaries, creating a master-detail relationship is not applicable here since the standard Account-Contact relationship is a lookup, and changing it to master-detail is not possible. Option C (Formula field limit reached on the Account object): This would limit the number of formulas but is not the root cause of the issue described. Option D (More than 5,000 characters in the formula): This limit refers to formula field complexity, but it does not explain the inability to reference child records. In summary, the limitation is due to Salesforce not allowing formula fields to reference child records.


Formula Field and Relationship Limits



Universal Containers' app builder has been tasked with replacing workflow rules and Apex triggers with Process Builders where possible.
What are two important considerations an app builder should know before the project is started? Choose 2 answers

  1. Avoid generating infinite loops.
  2. Apex has a different SOQL query limit than Flow.
  3. Create a process for each workflow rule.
  4. Combine actions when possible.

Answer(s): A,D

Explanation:

Before replacing workflow rules and Apex triggers with Process Builders, the app builder should consider avoiding generating infinite loops and combining actions when possible. Infinite loops can occur when a process updates a record that causes another process to run on the same record, and so on. Combining actions can reduce the number of processes and improve performance and maintainability



Universal Containers wants to improve the process to create Opportunity records related to an Account. Many fields can be populated based on the Account record. Some fields require input from the user.
What should an app builder configure to meet the requirement?

  1. Process Builder triggered from Opportunity update
  2. Quick Action on the Account object
  3. Quick Action on the Opportunity object
  4. Process Builder triggered from Account update

Answer(s): B

Explanation:

A quick action on the Account object can be used to create Opportunity records related to an Account. The quick action can pre-populate some fields based on the Account record, and also allow the user to input some fields. This would improve the process of creating Opportunity records



The convert button on leads should NOT appear until the lead status picklist is set to a qualified.
What should an app builder suggest to meet these requirements?

  1. Picklist dependency, page layouts, record types
  2. Custom button, validation rule, record types
  3. Process builder field update, quick action, record type
  4. Page layout, record types, process builder field update

Answer(s): B

Explanation:

A custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses



Viewing page 22 of 60
Viewing questions 106 - 110 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!