Salesforce CRT-403 Prepare for your Platform App Builder Certification Exam Practice Test

Answer : C

To manage field editability based on the opportunity status:

C . Use field-level security on page layouts with record types to restrict editing fields. This combination allows for different layouts and editable fields based on the status of the record (e.g., closed or open).

Steps to implement:

Create or adjust record types for open and closed opportunities.

For each record type, create a specific page layout.

On the page layout for closed opportunities, set the majority of fields to read-only using field-level security, except for the 'Post-Close Follow-up Date' and 'Post-Close Follow-up Comments' fields.

Assign the appropriate page layouts to the respective record types.

Update profiles or permission sets to use these record types and page layouts accordingly.

This setup ensures that sales reps can modify fields only when the opportunity is open, and the sales operations team can edit specific fields after closure.

For more information on using record types and page layouts, check Salesforce's documentation on Record Types.

Answer : B

To ensure data integrity where the Region field on the Contact object needs to be filled out conditionally based on the parent Account's status, a validation rule on the Contact is the most effective method:

B . Create a validation rule on Contact. This rule can enforce that the Region field must be filled out for Contacts related to Accounts marked as 'High Priority'.

Steps to create this validation rule:

Navigate to Setup Object Manager Contact Validation Rules.

Create a new validation rule.

In the formula, use:

AND(

ISPICKVAL(Account.Customer_Status__c, 'High Priority'),

ISBLANK(Region__c)

) )

Provide an error message to display when the rule is violated.

Save and activate the rule.

This validation rule checks that if a Contact is associated with an Account marked 'High Priority', the Region field cannot be blank.

For further detail, Salesforce's Validation Rule Considerations provides additional guidance.

Answer : C

When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity:

C . The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll-up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed.

To resolve this, follow these steps:

Identify and delete all roll-up summary fields on the Account object that reference the Park object.

Convert the master-detail relationship to a lookup relationship.

Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries.

For more guidance, review Salesforce's documentation on Changing Field Types.

Answer : B

To import leads while preventing duplicates:

B . Data Import Wizard is the appropriate tool. The Data Import Wizard in Salesforce includes functionality to check for duplicates based on matching records by certain criteria (like email or lead ID) during the import process, thus preventing duplicate lead records from being created.

More details on using the Data Import Wizard can be found in the Salesforce Data Import Wizard guide.

Answer : B

To manage frequently changing picklist values effectively:

B . Set up Global Values in Picklist Value Sets. This approach allows for centralized management of picklist values that can be reused across multiple fields and objects. By using global value sets, inactive values can be efficiently managed and deactivated without impacting fields that use these sets.

For further information on managing picklists, check Salesforce's Picklist Management guide.

Answer : D

The 'Accordion' Lightning component is designed to break up content into collapsible sections. This component would be suitable for managing the visibility of large numbers of fields by grouping them into separate tabs or sections that can expand and collapse. This makes navigation easier and declutters the interface.

A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields.

B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields.

C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

Answer : C

Formula fields in Salesforce can use various functions including text, mathematical, and logical functions to create simple or complex expressions. They can handle data from fields of the same record. Option C, 'A combination of the Opportunity's Text and a Description fields,' is a valid configuration for a formula field as it involves simple concatenation of text fields, which is supported. Options A, B, and D exceed the capabilities of formula fields:

A: Hyperlinks to other objects using formula fields do not directly support navigation to parent records of a different object.

B: Rich Text and HTML formatting are not supported in formula fields.

D: Formula fields have limits in their complexity and field references which would make mixing numerous fields from different related objects impractical and likely exceed formula size limits. Reference: Formula Field Overview on Salesforce Developer Guide