Pass the Salesforce App Builder Platform-App-Builder Questions and answers with CertsForce

The validation must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

The correct answer is B. Use a private sharing model granting record access using hierarchy; manage field access with field-level security.

Cloud Kicks needs two different layers of access control:

First, only the sales rep, their manager, and executives above the manager should view the scorecard record. That is a record-level access requirement. A private sharing model with access opened through the role hierarchy supports this because users above a record owner in the hierarchy can access subordinate-owned records. Salesforce states that the role hierarchy opens access vertically to users higher in the hierarchy.

Second, reps must not see the executive comment fields. That is a field-level access requirement, so it should be handled with field-level security. Salesforce separates record-level access from field-level permissions.

A and C are incorrect because custom settings are not used to grant record access. D includes record types, but record types do not secure individual fields; field-level security is required.

===========

The correct answer is B. Lookup.

This is a one-to-many mentorship relationship: one experienced Realtor can mentor many new Realtors, but each new Realtor works with only one experienced Realtor. A lookup relationship is appropriate for connecting one record to another in this type of flexible parent-child model. Salesforce relationship documentation confirms that lookup relationships are used to relate objects without the strict ownership, sharing, and deletion behavior of master-detail relationships.

Master-detail is too restrictive because the new Realtor record should not necessarily inherit ownership and deletion behavior from the mentor. Many-to-many is incorrect because each new Realtor has only one mentor. Indirect lookup is used for external objects, not this internal Salesforce relationship.

===========

The correct answer is B. Universal Containers has internal Account OWD set to Public Read/Write, which lets internal users broadly access Account records. However, Experience Cloud / customer community users can have a separate external sharing model. Salesforce documentation explains that External Organization-Wide Defaults provide separate default access for external authenticated users so companies can better secure data for community users.

Setting the Account external OWD to Private prevents customer community users from seeing all company Account records by default.

Why others are incorrect:

A record types do not control record visibility.

C an owner-based sharing rule would grant more access, not restrict default access.

D permission sets grant object/field permissions; they do not replace OWD record-sharing control.

===========

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========

The correct answer is B. Approval Process.

An Approval Process is used when a record must be reviewed and approved before moving forward. Salesforce Trailhead gives a very similar example: opportunities with high discounts requiring approval before proceeding.

Here, Cloud Kicks needs CFO sign-off when a major shoe retail deal has a discount greater than 30% before it can be closed. This is exactly what an approval process is designed to handle.

Why others are incorrect:

Slack message only sends communication.

Email alert only notifies someone.

Field update changes a field value but does not collect formal approval.

===========

The correct answer is C. Checkbox.

Universal Containers needs to track whether a contract was sent or not sent before an Opportunity is marked Closed Won. This is a simple Yes/No reporting requirement, so a Checkbox field is the best field type. Salesforce checkbox fields are represented as True/False values and can be used in reports and list view filters.

Picklist is unnecessary for a two-state value. Text and Text Area would create inconsistent reporting because users could type different values.

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

A validation rule is required because Cloud Kicks needs to prevent , rather than merely discourage, users from skipping required Opportunity stages. A validation formula can evaluate the new StageName together with the prior stage, required fields, or other process criteria and block the save when the transition violates the sales process. Salesforce validation rules are designed to prevent records from being saved when specified business conditions are violated. Path and Guidance for Success improve usability and tell representatives what they should do, but neither inherently stops a user from jumping directly to Contract Signed. An approval process would add unnecessary managerial routing and does not directly represent the requirement to enforce valid stage progression. Therefore, a validation rule is the most efficient declarative mechanism for enforcing the required pipeline sequence.

================