App Builder Platform-App-Builder Book

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. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.

Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.

Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.

B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.

D is incorrect because “20 object references” is not the key roll-up summary consideration in this proposal.

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.

===========

Feed Tracking is the correct feature because Salesforce can automatically generate feed updates when a tracked field changes on a record. Salesforce Help explains that feed tracking detects changes to tracked record fields and posts updates to the feed. It can also be configured for custom objects.

For this scenario, the app builder would track the travel request approval/status field. When the request becomes Approved, Salesforce posts that tracked change automatically on the record feed.

Why others are incorrect:

Auto-response rule sends automatic email responses, mainly for Lead/Case scenarios.

Approval process manages record approval routing, but the feature that creates automatic feed posts for field changes is Feed Tracking.

Feed quick action is manual, not automatic.

===========