Selected Platform-App-Builder App Builder Questions Answers

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

When deploying from a sandbox on a newer Salesforce version to production on a current version, any components that rely on features not yet available in production will fail.

Change sets do not automatically upgrade production.

All features must be supported in the target org at deployment time.

Salesforce documentation notes that compatibility issues may occur if components use version-specific features, and deployments must be tested against the target org’s current version. (Salesforce Help)

A is incorrect because deployments do not automatically wait for production upgrades.

B is partially true, but deployments are possible if features are supported.

C is incorrect; components are not automatically upgraded.

===========

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 A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========