Plat-Admn-202 Exam Preparation Material | Salesforce Certified Platform App Builder

Explanation:
Creating a formula field on the Contact object and setting the value of the formula to TEXT(Account.Account_Region__c) would reflect the region of the related account on the contact record and stay in sync if the value changes on the account. This is the most efficient and maintainable way to meet the requirement. Creating a workflow rule or a picklist field would require additional configuration and complexity

Explanation:
For automatically updating contact statuses when an account type changes:
D. Record triggered flow. This type of automation can monitor changes in account types and accordingly update related records, such as contacts.
Steps to implement:
Navigate to Setup → Flows.
Create a new Flow and choose the record-triggered flow type.
Configure the flow to trigger when the Account record is updated to 'Past-Customer'.
Add an Update Records element to modify all related contacts, setting their status to 'Re-Market'.
Activate the flow.
This automation ensures that contact statuses are updated in real-time when their related account's type changes, maintaining data consistency and relevancy.
For more on record-triggered flows, check out Salesforce's Record-Triggered Flows documentation.

Explanation:
For a formula to evaluate to true when the stage is set to "Negotiation/Review" and the close date is less than one week away, the correct formula is:
Option
B. This formula uses the ISPICKVAL function to check the text value of a picklist and compares the CloseDate to a week from today:
AND( I AND(
ISPICKVAL(StageName, "Negotiation/Review"),
CloseDate - 7 < TODAY()
)SPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() )
This formula checks that both conditions are met: it confirms the stage name is "Negotiation/Review" and that the CloseDate is within the next 7 days from the current date.
Option A lacks the ISPICKVAL function necessary for evaluating picklist fields.
Option C uses DAY(7) which is not a valid Salesforce formula expression.
Option D also uses DAY(7) incorrectly and fails to use the ISPICKVAL function.
Reference for creating formula fields in Salesforce:
Formula Field
Reference: https: //help.salesforce.com/articleView?id=sf.customize_functions.htm&type=5

Explanation:
To track the total number of trails associated with a park without writing code, the correct actions to take are:
Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.
Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.
A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.
For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:
Master-Detail Relationship:
https: //help.salesforce.com/articleView?id=relationships_considerations.htm&type=5
Roll-Up Summary Fields:
https: //help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm&type=5

Explanation:
The requirement is time-based (Case in New status > 4 business hours) and requires a notification.
Escalation Rules can monitor case age and trigger escalation or notifications after a specified period.
Flow Builder (Scheduled Path or Scheduled Trigger Flow) can be used to evaluate business hours and send alerts.
Why B (Escalation Rules) is correct: Exact Extract: “Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” ― Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.
Why B (Escalation Rules) is correct: Exact Extract: “Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” ― Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.
Why D (Flow Builder) is correct: Exact Extract: “Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.”
― Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”
Why D (Flow Builder) is correct: Exact Extract: “Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.”
― Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”
Why not A: Validation Rules prevent saving invalid data but cannot evaluate elapsed time.
Why not C: Scheduled Apex would work technically but is a code-based solution; declarative automation (Flow or Escalation) is preferred for App Builder certification.
Reference: Salesforce Help | Case Escalation Rules
Salesforce Help | Scheduled Paths in Flow Builder
Salesforce Platform App Builder Exam Guide | Business Logic and Process Automation