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

The correct answers are C. Currency, D. Date, and E. Percent.

Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.

Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct answer is D. Custom Report Type.

A custom report type defines which records and fields are available in a report based on relationships between a primary object and related objects. Salesforce also references custom WITH or WITHOUT report types for reporting on related records.

Because DreamHouse Realty needs “with” or “without” reports involving a custom object and related lookup data, the app builder must create a Custom Report Type and define the object relationships.

Why others are incorrect:

A. Report Filters filter report results but do not define the reportable object relationship.

B. Row-Level Formula calculates values per row; it does not create with/without relationship reporting.

C. Report Bucket Field groups report values; it does not define related-object report structure.

===========

The correct answer is C. Apex unit test failures.

Because the unmanaged package was successfully installed in a Full Copy sandbox that matches production, issues like feature incompatibility, license mismatch, or object limits would normally have appeared during sandbox testing. The remaining Salesforce-specific production blocker is Apex test execution.

Salesforce deployment documentation states that if any Apex test fails, the deployment is rolled back. Salesforce Apex testing guidance also states that Apex unit tests must meet coverage requirements and complete successfully for deployment or packaging scenarios.

So the package failed in production because the required Apex tests did not complete successfully.

===========

The correct answer is B. Feed Tracking.

DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c , to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.

Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.

A. Topics is used for categorizing Chatter posts, not automatically tracking field changes.

C. Pin Field is not the Chatter feature for tracking field updates.

D. Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.

===========

The correct answers are B. Roles and Subordinates, C. Public Groups, and D. Users / Individual Users.

Salesforce manual sharing allows record owners or users with proper access to share individual records with users, public groups, and roles. Salesforce documentation specifically states that manual sharing is used to share individual records with other users, public groups, and roles.

For Lightning manual sharing, Salesforce also describes entering groups, users, roles, or territories in the sharing search box.

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

A. Permission Set Groups is incorrect because permission set groups grant object, field, app, and system permissions, not case-by-case record sharing.

E. Private Groups is not the standard answer for this Platform App Builder manual-sharing question.

===========

The correct answer is A because Case_Issue__c is described as a junction object. In Salesforce, a junction object is typically built with two master-detail relationships to model a many-to-many relationship.

Salesforce documentation states that sharing access to a junction object record is determined by the user’s sharing access to both associated master records and the sharing setting on the relationship fields.

So, for auditing users to view Case_Issue__c records, they need read access to both parent/master records: Case and Issue__c.

Why others are incorrect:

B misses access to Issue__c.

C includes only the junction object and misses both parent/master records.

D misses access to Case.

===========