Salesforce CRT-403 Exam Questions
Prepare for your Platform App Builder Certification (Page 5 )

Updated On: 16-Feb-2026

An app builder wants to add the option to 'Send New Email' from Leads, Contacts and Accounts for users on mobile.
What is the benefit of using global actions to accomplish this?

  1. Global actions can be accessed anywhere actions are pages, feed and Chatter groups,
  2. Salesforce Lightning Component Library houses existing global actions prebuild for use.
  3. The global action's layout automatically clones the default page layout.
  4. Global actions are record-specific and are available when searching that particular

Answer(s): A

Explanation:

Global actions can be accessed anywhere actions are pages, feed and Chatter groups. This is correct because global actions are not tied to a specific object, and they can be added to any page that supports actions, such as record pages, home pages, feed pages, and Chatter groups.



An app builder has a custom component they want to make available on the utility bar, but the component is unavailable.
How should the component be tagged?

  1. For use on record pages.
  2. For use in Lightning App Builder.
  3. For use on the utility bar.
  4. For use in App Manager.

Answer(s): C

Explanation:

To make a custom component available for the utility bar in Salesforce, the component needs to be explicitly tagged for use in the utility bar. Salesforce components require specific configurations to be available in different parts of the application, such as the utility bar, record pages, or app pages. Option C: For use on the utility bar: When a custom Lightning component is developed, it must include a specific target tag in its .js-meta.xml configuration file that marks it as usable in the utility bar. This is done by setting the target to "lightning__UtilityBar". Without this tag, the component will not appear as an option to add to the utility bar in the App Manager. Example of how the component is tagged in the meta.xml file:
xml
Copy code
<targets>
<target>lightning__UtilityBar</target>
</targets>


Reference:

Utility Bar Components Documentation
Option A: For use on record pages: This tag makes the component available only on record pages, but not the utility bar. The component would have a target for lightning__RecordPage in this case. Option B: For use in Lightning App Builder: This option would allow the component to be used in the Lightning App Builder, but it wouldn't make the component available for the utility bar. App Builder placement is typically for page layouts.
Option D: For use in App Manager: This is incorrect, as App Manager is used for managing apps and not for tagging components for availability.
In summary, to make the component available for the utility bar, it needs to be specifically tagged for that purpose using the lightning__UtilityBar target in the component's metadata file.


Utility Bar Metadata Configuration



Universal Containers has a custom picklist called Support Level on the Account object. They would like to show the real-time value of Support Level on all case records.
How should an app builder implement this requirement?

  1. Create a formula field on the Case object using the TEXT function.
  2. Create a formula field on the Account object using the ISPICKVAL function.
  3. Create a Process Builder and use a field update on the Case object.
  4. Create a roll-up summary field using Support Level on the Account object.

Answer(s): A

Explanation:

Create a formula field on the Case object using the TEXT function. This is correct because a formula field can reference a field from a related object using dot notation, and the TEXT function can convert a picklist value to text. This way, the case record will always show the current value of the Support Level field on the account record.



UC has a requirement that an opportunity should have a field showing the value of its associated account's billing state. This value should not change after the opportunity has been created. Is there a recommended solution to configure this automated behavior?

  1. Formula field
  2. Apex
  3. Workflow
  4. Roll-up summary field

Answer(s): C

Explanation:

Apex. This is correct because Apex is a programming language that can perform complex logic and manipulate data in Salesforce. Apex can be used to create a trigger on the opportunity object that copies the value of the billing state from the related account record when the opportunity is created, and prevents it from being changed afterwards. The other options are not suitable for this requirement because they either cannot copy data from a related object (formula field, roll-up summary field) or cannot prevent data from being changed (workflow).



Universal Containers has a new custom object for Invoices that includes an Invoice Number field, Before the Invoice object can be used, invoices will be migrated from an external system maintaining their current Invoice Number. After the migration, salesforce will be the system of record and each new Invoice created in Salesforce must have a unique Invoice Number. How should the app builder configure the Invoice Number field?

  1. Create a Text filed for the original Invoice Number and an AutoNumber field for the Salesforce Invoice Number.
  2. Create a Text field and mark it as a unique external ID field.
  3. Create a Text field, then change it to AutoNumber after the migration.
  4. Create an AutoNumber field and migrate the Invoices

Answer(s): B

Explanation:

The Invoice Number field should be a Text field and marked as a unique external ID field. This will allow the migration of invoices from an external system while maintaining their original Invoice Number. It will also ensure that each new Invoice created in Salesforce has a unique Invoice Number.






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

Join the CRT-403 Discussion