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

Moving the reports from the Unfiled Public Reports folder and adding them to a new change set is what the app builder should do to deploy the reports to production. According to the Salesforce documentation, “Reports in the Unfiled Public Reports folder aren’t available for deployment.” Moving the reports to the Untried Public Reports folder, recreating the reports in production, and adding the reports to an unmanaged package are not necessary or recommended actions.

As of the Winter '24 release, Salesforce introduced the ability to send outbound messages directly from Flow. This makes Flow the best choice for automating the notification to an external system when a lift is sold, fulfilling the need for both checking the custom To Be Installed checkbox and sending the notification the next day.

Flow: With this new functionality, Flow is now the most versatile automation tool for this use case. You can:

Create a scheduled path that triggers the next day after the lift is sold (e.g., when a record meets the criteria such as the checkbox being checked).

Send the outbound message to notify the external system about the lift installation.

Perform all of this declaratively, replacing the need for Workflow, which previously was the go-to for outbound messages.

Why not Workflow anymore? Although Workflow still supports outbound messages, Flow is the preferred tool now, as Salesforce is deprecating Workflow rules and Process Builder in favor of Flow. Flow also allows for more complex logic and actions, providing flexibility in future-proofing automation.

Winter '24 Flow Outbound Message

Dynamic actions are a new feature that allow app builders to create custom buttons or actions that can call Lightning Web Components and display them conditionally based on field values or other criteria. Formula fields, AppExchange products, and custom links are not able to call Lightning Web Components.

 Big objects and external objects can be used to archive historical data and reduce data storage in Salesforce, while still allowing users to access the archived data using reports, queries, and lookups. Big objects store data within Salesforce, while external objects store data outside Salesforce and integrate it with Salesforce using an external data source

Workflow rule and an outbound message or Process Builder and Apex Code are two ways to integrate Salesforce with an external web service. Workflow rule can define criteria and actions for triggering an outbound message, which is an XML message sent to a designated endpoint URL. Process Builder can invoke Apex Code, which is a programming language that can make callouts to external web services using HTTP requests. Flow Builder and an outbound message or Process Builder and an outbound message are not possible combinations.

When a master-detail relationship is created between two objects, Salesforce automatically creates a standard report type that allows users to report on the parent and child together.

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why not B:The parent-to-child relationship drives the report type. A “Star__c with Galaxy__c” type is not automatically created.

Why not C or D:Custom report types are only needed if you want to include additional related objects or modify relationships; Salesforce automatically provides one for master-detail pairs.

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source