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

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

The correct answer is C. Research and evaluate data enrichment products on the AppExchange to automate data entry.

The sales manager wants reps to spend less time manually entering business-card information while maintaining data quality. Salesforce AppExchange is the correct place to evaluate packaged solutions that extend Salesforce functionality. Trailhead describes AppExchange as a place to find solutions for business needs, and AppExchange contains business-card scanning apps that can create or match Salesforce Leads, Contacts, and Accounts with reduced manual entry.

A does not automate data entry.

B is not the best fit because Flow cannot read business cards by itself.

D is incorrect because formula fields calculate values from existing data; they do not capture business-card information.

===========

The correct answer is D. For use on the utility bar.

For a custom Lightning web component to appear as an available component in the utility bar, it must be exposed in its metadata configuration with the lightning__UtilityBar target. Salesforce developer documentation states that lightning__UtilityBar enables a component to be used as a utility item in an app’s utility bar, and the component must be exposed with the appropriate target.

B. For use in Lightning App Builder is broader and not enough by itself for utility-bar availability. C. For use on record pages exposes the component for record pages, not the utility bar. A. For use in App Manager is not the correct component target wording.

===========

A Data 360-triggered flow is designed to start when specified conditions are met on a Data 360 Data Model Object rather than on a standard Salesforce database record. Salesforce documentation describes this flow type as automation that responds to changes occurring in a DMO or calculated insight and uses Data 360 data actions/events to initiate the flow. The app builder can select the loyalty DMO, define a condition such as Tier = Diamond, and then execute the required Salesforce actions when that data changes. A Salesforce record-triggered flow would require a Salesforce record change, which the question explicitly excludes. A schedule-triggered flow would introduce polling rather than near-real-time behavior, and a template-triggered prompt flow is intended for Prompt Builder. Therefore, Data 360-triggered flow is the appropriate architecture. Salesforce

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

The verified current-platform answer is D. Salesforce Conditional Field Formatting in Lightning App Builder allows Dynamic Forms fields to display configurable icons and colors according to rules and criteria. Critically, Salesforce explicitly supports formula fields when the formula resolves to a supported data type, so the existing formula field can drive the formatting rules. The app builder can configure different icons and icon colors without embedding presentation logic into the formula itself. IMAGE() and CASE() can produce formula-based images, but they are an older technique and do not provide the native Dynamic Forms conditional-formatting capability described by the current platform. Field help is static, and Screen Flow is unnecessarily complex.

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

The correct formula is TEXT(Galaxy__r.Type__c) .

The parent field Type__c is a picklist. In Salesforce formulas, a picklist value cannot be displayed directly as plain text unless it is converted with the TEXT() function. Salesforce documentation states that TEXT() converts picklist values to text in supported formula contexts. Cross-object formulas can reference fields from related parent records, so the child object Star__c can reference the parent Galaxy__c field using the relationship syntax Galaxy__r.Type__c .

VALUE() is for converting numeric text into a number, ISPICKVAL() checks whether a picklist equals a specific value, and FIND() searches text. None of those displays the parent picklist value as text.

===========

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

This is a classic many-to-many relationship requirement: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce recommends using a junction object for many-to-many relationships. A junction object is a custom object with two master-detail relationships.

The new custom junction object would sit between Contact and Solar Project, with one master-detail relationship to Contact and one master-detail relationship to Solar Project.

C could technically connect records using lookups, but the standard Salesforce data-modeling answer for a true many-to-many relationship is a junction object with two master-detail relationships.

===========

Performing Data Manipulation Language operations such as Update Records inside a Loop is a classic Flow governor-limit anti-pattern. Each loop iteration can perform another database operation, rapidly consuming transaction limits when a large collection of Opportunities is processed. Salesforce ' s official Flow guidance explicitly says never to place DML operations inside loops. Instead, the app builder should iterate through the records, use Assignment elements to modify them and add them to a record collection, and perform one bulk Update Records operation after the loop. Fault paths improve error handling but do not prevent governor-limit consumption. Schedule-triggered flows can update standard objects, so D is incorrect. The scalability problem described is therefore directly caused by performing Update Records repeatedly inside the Loop element.

The correct answers are A. Public Groups, D. Roles and Subordinates, and E. Users.

For a custom object with Private sharing, manual sharing is used to open access to selected records on a case-by-case basis. Salesforce manual sharing allows individual records to be shared with users, public groups, and roles. Salesforce Classic manual sharing also lets the user select the type of group, user, role, or territory to add.

B. Private Groups is not the standard Platform App Builder answer here.

C. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

The correct answer is A. Flow.

The requirement says the Opportunity should store the Account Billing State value, but the value must remain static after the Opportunity is created. A record-triggered Flow is the recommended declarative automation because it can run when an Opportunity is created and populate a custom field with the related Account’s Billing State. Salesforce Trailhead describes record-triggered flows as automation that can run when a record is created or updated, and can update the triggering record or related records depending on configuration.

D. Formula field is incorrect because formula fields are automatically calculated and read-only. A formula would continue to reflect the current Account Billing State, so it would not preserve the original value after creation.

B. Apex is not the recommended first choice because Flow handles this requirement declaratively.

C. Roll-up summary field is incorrect because roll-ups aggregate child records; they do not copy a parent Account field value onto an Opportunity.