Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 4

The correct answer is C. Two Master-detail relationships on a new custom object.

This is a many-to-many relationship: one Contact can be related to many Solar Projects, and one Solar Project can be related to many Contacts. Salesforce’s standard declarative design for many-to-many relationships is a junction object. A junction object is a custom object with two master-detail relationships connecting the two related objects.

A is incorrect because the two master-detail relationships belong on the new junction object, not directly on Contact and Solar Project.

B can technically relate records, but it is not the standard Salesforce many-to-many model tested here.

D does not correctly create a scalable many-to-many model.

===========

The correct answer is A. Partial Copy.

A sandbox template is used to define which object data is copied into a sandbox. Salesforce documentation states that sandbox templates control what data is copied into Full or Partial Copy sandboxes. Since the question says the app builder created a sandbox template for Accounts, Projects, and Project Milestones, the correct testing environment is Partial Copy because it includes metadata plus a selected sample of production data defined by the sandbox template. Developer, Developer Pro, and Scratch Orgs do not use sandbox templates for selected production data in this way.

===========

The correct answer is B. Unable to reference the child records.

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========

The correct answer is A. Build a global action to create Contacts.

Sales reps need a fast mobile-friendly way to create new Contact records and complete additional details later. A global quick action is the best fit because it lets users create records quickly without needing to navigate deeply into the app. Salesforce documentation states that global actions allow users to create or update records without leaving the page they are on. Salesforce also documents that Create a Record global actions let admins choose the object to create, such as Contact.

Salesforce mobile uses quick actions in the action bar/action menu, making them suitable for fast record creation on mobile.

B. Path is used for guided stages, not quick contact creation. C. Mobile menu customization improves navigation but does not simplify the create process enough. D. Compact layout controls key field display, not fast record creation.

===========

The correct answer is A. TODAY().

The formula needs to calculate how many whole days have elapsed since a marketing communication was sent. The TODAY() function returns the current date as a Date value, which is appropriate for whole-day calculations. Salesforce documentation also shows that TODAY() can be used with addition and subtraction operators for date calculations.

NOW() returns a Date/Time value and can introduce fractional day/time calculations. DATEVALUE() converts a Date/Time or text value into a Date, but the question asks which function should return today’s date for calculating elapsed days. DATETIMEVALUE() returns a Date/Time value, not the desired whole-date calculation.

===========

The correct answer is C.

The app builder needs to display only the first five digits from the parent Account’s ZIP+4 custom text field. Salesforce’s LEFT() function returns a specified number of characters from the beginning of a text string, so the correct formula is:

LEFT(Account.Zip_Code__c, 5)

Salesforce formula documentation confirms that LEFT returns characters from the beginning of a text string.

BEGINS() checks whether text starts with specific characters. LPAD() pads text to a specified length. TEXT() converts certain data types to text, but it does not extract the first five characters.

===========

The correct answer is A. Make the Opportunity Type a required field on the initial Opportunity page layout and use automation to update the record type based on the Opportunity Type.

The requirement has two phases: first, show users only the fields needed to create the Opportunity; after save, show the full record page based on the Opportunity type. This can be handled by using a required Opportunity Type field first, then automation can update the Opportunity record type. Salesforce page layouts can be assigned by profile and record type, which allows different Opportunity types to show different layouts after the record type is set.

B is incomplete because it only mentions page layouts based on profile, not dynamically changing the layout based on Opportunity Type after creation. C is incorrect because sharing rules control record access, not field display. D relies on users manually expanding sections and does not meet the streamlined requirement.

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

The correct answer is D. Patch.

In application lifecycle management, patch releases are used for bug fixes and simple, low-impact changes. Salesforce packaging documentation also describes patch versions as minor upgrades used for fixing bugs or errors.

Major releases are for large changes or significant new functionality. Minor releases are usually for limited-impact enhancements. Roll is not the correct ALM release category here.

===========