Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

 Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field is the recommended method for the app builder to achieve the request of rolling up sales metrics to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active. According to the Salesforce documentation, “Roll-up summary fields calculate values from related records, such as those in a master-detail relationship.” A roll-up summary field can filter on a field value of the child records and sum up only those records that match the criteria. Utilize the AppExchange to download a third-party application that can roll up the sales dollars with the appropriate filter, create a lookup relationship between the parent and child object with a roll-up summary field that filters on the status field, and utilize Apex code to roll up the desired amounts are not valid or necessary methods for this request.

Users will be unable to view the Account Interest records or the Interest records because they do not have read access to the Interest object. This is a standard behavior of Salesforce when a user does not have access to a related object.

The validation rule should check if the user role is not Marketing, and if the Retail Opt In field has been changed to Yes. The ISCHANGED function returns true if the field value has been changed, and the ISPICKVAL function returns true if the field value matches a specified picklist value. 

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.

To automate the submission of opportunities into the "Secure Commitment" stage and eliminate manual submission for approval, the best feature to use is:

Record-Triggered flow optimized for Actions and Related Records (D). This type of flow allows for complex automation that can include submitting records for approval based on specific criteria being met, such as reaching a particular stage in the opportunity lifecycle. It's particularly suitable for handling related record updates and other actions like submissions for approval, which are integral when an opportunity reaches a certain stage.

Record-Triggered Flow optimized for Fast Field Updates (A) is focused primarily on quick updates to fields and may not handle the complexity of submission for approval processes adequately. Custom button and screen flow (B) could be used to manually trigger processes but does not automate the submission. Platform Event-Triggered flow (C) is typically used for integrations and reacting to system-wide events, not for standard record lifecycle management.

Reference for using Flows in Salesforce, particularly for automating business processes like approval submissions:

Record-Triggered Flows: https://help.salesforce.com/articleView?id=sf.flow_considerations_trigger_record.htm &type=5

Sharing rules and manual sharing are two features that can extend record access beyond the organization-wide defaults. Sharing rules are automatic rules that grant access to groups of users based on certain criteria, such as role, public group, or territory. Manual sharing is a manual way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy. Option B and C are not features that extend record access.

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

 The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.

The app builder should create a master-detail relationship field on the gift card object to support the requirement. A master-detail relationship field creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record. In this case, the Account object would be the master and the gift card object would be the detail. By creating a master-detail relationship field, the app builder can meet these requirements:

Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.

Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.