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

The app builder should add the fields to the page layout on the object to ensure users can access the new object and fields. The page layout determines which fields are visible and editable on the record detail page. Option A, B, and C are not necessary for this purpose.

The new custom object (“Installation__c”) must store installation details that are related to an Opportunity. Since each installation should be tied directly to a single opportunity, and inherit ownership and visibility from that opportunity (as per “sales reps should have visibility”), a Master-Detail relationship is appropriate.

Why B (Master-Detail) is correct: Exact Extract: “In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships Overview Because Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations. Exact Extract: “The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why B (Master-Detail) is correct: Exact Extract: “In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships Overview Because Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations. Exact Extract: “The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why not A (Many to Many): Many-to-many relationships are only used when multiple records on both sides need to relate (e.g., Opportunities linked to multiple Installations and vice versa). That is not described here.

Why not C (Hierarchical): Hierarchical relationships are only available on the User object.

Why not D (Lookup): Lookup relationships do not automatically grant visibility or inherit ownership, so sales reps might not see all related installations.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Relationships Overview

Salesforce Help | Master-Detail Relationships

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

 One of the easiest ways to display real-time stock price for each account is to install a solution from the AppExchange, such as Stock Price Lightning Component3. This component can be added to any record page using the Lightning App Builder.

Schema Builder is a tool that allows app builders to view and modify the data model of their Salesforce org. Some of the capabilities of Schema Builder are:

Creating and editing custom objects and fields

Creating and editing relationships between objects

Showing selected objects on a page

Editing custom settings

Schema Builder cannot be used to create a new record type or view page layouts in a new window.

The requirement specifies:

Subset of production data (not all data)

Under 5 GB of data

Periodic refresh (every weekend)

A Partial Copy sandbox fits these requirements perfectly — it includes sample data defined by a sandbox template, up to 5 GB, and has a refresh interval of 5 days (the shortest interval available besides Developer types).

Why A (Partial Copy) is correct: Exact Extract: “A Partial Copy sandbox includes your organization’s metadata and a sample of your production data as defined by a sandbox template. The maximum size is 5 GB and the refresh interval is 5 days.” — Salesforce Help | Sandbox Types and Templates

Why not B (Full Copy): Full Copy includes all production data and has a 29-day refresh interval.

Why not C or D: Developer and Developer Pro sandboxes contain metadata only and no production data.

The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.

 Before replacing workflow rules and Apex triggers with Process Builders, the app builder should consider avoiding generating infinite loops and combining actions when possible. Infinite loops can occur when a process updates a record that causes another process to run on the same record, and so on. Combining actions can reduce the number of processes and improve performance and maintainability

To ensure that opportunities are submitted into the approval process when their close date is pushed more than 30 days, an app builder should use an automated process to submit the record for approval. An automated process can be created using tools such as Process Builder or Flow Builder, and it can define the criteria and actions for submitting a record for approval. [Source]

Create mobile navigation menus for both the sales and marketing profiles. This is correct because mobile navigation menus allow users to customize the items that appear in the navigation bar of the Salesforce mobile app, and they can be assigned to different profiles.