Master Salesforce Platform App Builder Plat-Admn-202 Certification Fast

Correct : D, D

To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:

Correct : C

The requirement is to copy the parent Account's Billing State onto a custom field on Opportunity at the moment the Opportunity is created, and keep that value static thereafter.

Why not Formula (B): A formula would always recalculate, so the value would change if the Account's Billing State later changes.Exact Extract: ''Formula fields are read-only fields that automatically recalculate their values when any referenced fields change.'' --- Salesforce Help | Formula Fields

Why not Roll-Up Summary (A): Roll-up summary fields only summarize child records onto a master (parent) record; they do not copy values from a parent (Account) down to a child (Opportunity), and they can't summarize a text/state value.Exact Extract: ''A roll-up summary field calculates values from related records, such as those in a related list, on a master record.'' --- Salesforce Help | Roll-Up Summary Fields

Why Flow (C) is correct: A Record-Triggered Flow on Opportunity (when a record is created) can set a field value by referencing the related Account (e.g., Opportunity.Account.BillingState) and writing it into a dedicated ''snapshot'' field (e.g., Billing State at Create__c). Because this is a one-time assignment on create, the value remains static unless intentionally updated by further automation.Exact Extract 1: ''Use Flow Builder to automate business processes by collecting data and performing actions in your Salesforce org.'' --- Salesforce Help | Flow BuilderExact Extract 2: ''Record-triggered flows launch when a record is created, updated, or deleted, and can update fields on the triggering record.'' --- Salesforce Help | Record-Triggered Flows

Why Apex (D) is not preferred: While Apex could do the same copy-on-create, Salesforce's recommended approach is to use declarative automation (Flow) when possible.Exact Extract: ''Before considering Apex, evaluate whether your solution can be implemented with declarative tools such as Flow.'' --- Salesforce Architect Guidance | Clicks, Not Code

Implementation note (for clarity): Create a custom text field on Opportunity, e.g., Billing State at Create (Billing_State_at_Create__c). Build a Record-Triggered Flow:

Trigger: Opportunity --- ''A record is created''

Get or use the related Account from the $Record.AccountId relationship

Update the new Opportunity field with Account.BillingState

Do not run the flow on updates

Reference (Salesforce Platform App Builder documents / Study Guide topics):

Salesforce Help --- Formula Fields

Salesforce Help --- Roll-Up Summary Fields

Salesforce Help --- Flow Builder

Salesforce Help --- Record-Triggered Flows

Salesforce Architect Guidance --- Clicks, Not Code

Salesforce Platform App Builder Exam Guide --- Business Logic and Process Automation

Correct : D

Upon adding a lookup field to Account from a custom object, Box:

D . Accounts with Boxes. Salesforce automatically creates a new report type that reflects the relationship from the perspective of the parent object, in this case, Accounts, showing related Box records.

This new report type enables users to create reports that list Accounts along with their associated Boxes, if any.

For further understanding of report types and relationships, Salesforce's guide on Report Types provides comprehensive information on how these are structured following modifications to object relationships.

Correct : D

Salesforce Help - Account Hierarchies

Correct : C

A custom action on Account can be used to create additional accounts from a parent account record. A custom action can have predefined values for certain fields based on the parent record. A custom global action can be used to create records that do not have any relationship with other objects. A custom link on Account can be used to execute JavaScript or link to an external URL.