An app builder is preparing to deploy a new app from the sandbox to Production using change sets. Which two considerations should an app builder keep in mind during this process? Choose 2 answers
Answer : A, D
When deploying from sandbox to production using Change Sets, the following are critical considerations:
A . Transactions will revert if the deployment errors -- Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.
D . Change sets do not include all components and may require manual configuration -- Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.
Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)
B . Users being logged out is not required; deployments can occur while users are logged in.
C . Salesforce Connect does not automatically link environments; it is unrelated to change sets.
===========
Question 2
Sales reps want the ability to see who can view their account records and How the people have access. Which button should the app builder add to the Account page layout to enable this?
Answer : A
The correct answer is A. Sharing Hierarchy.
Sales reps want to see who has access to an Account record and why/how they have that access. Salesforce provides this through Sharing Hierarchy. Salesforce documentation states that users can click Sharing Hierarchy from the record action menu to display users who have access to the record. Salesforce release documentation also explains that selecting Sharing Hierarchy lets users view record access and the reason for that access.
C . Sharing is not the best answer because the Sharing button is mainly used to manually grant access, not to view the full access hierarchy and access reasons. B. New Task and D. Edit do not relate to record access visibility.
===========
Question 3
What are the limitations of Schema Builder when creating a custom object?
Answer : A
Schema Builder can create custom objects, relationship fields, formula fields, and normal fields, but a key limitation is that fields created through Schema Builder are not automatically added to the object's page layout. The app builder must go to the page layout separately and place the fields where users need to see them. Salesforce Trailhead confirms Schema Builder supports relationship fields, formula fields, and normal fields, so option B is incorrect. Salesforce Help also notes that fields added through Schema Builder are not automatically added to the page layout.
Question 4
Universal Containers manages leads in a Lead qualification queue where Sales reps can accept ownership of the Lea Campaign members are required to Have a sales owner. Which validation rule should an app builder configure?
Answer : C
The correct validation rule is:
AND(
ISNEW(),
ISBLANK(Lead.Owner:User.Id)
)
This rule prevents a new Campaign Member from being created when the related Lead does not have a User as owner. Leads can be owned by either a user or a queue, and Salesforce queues can own Lead records.
Salesforce validation rules block a save when the formula evaluates to True. The ISNEW() function checks whether the record is being created, and ISBLANK() checks whether the Lead owner's User Id is empty.
For owner fields in cross-object formulas, Salesforce requires being explicit about the owner type, such as Owner:User or Owner:Queue.
Why not others:
A is wrong because Lead.Owner.Id is normally populated whether the owner is a user or queue.
B and D focus on queue ownership, but the best exam answer checks that the Lead has an actual User owner when the Campaign Member is created.
Question 5
An app builder wants to streamline the user experience by reflecting summarized calculations of Specific fields on various objects. Which three field types can be used in roll-up summary fields to accomplish this? Choose 3 answers
Answer : C, D, E
The correct answers are C. Currency, D. Date, and E. Percent.
Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.
Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.
Question 6
A sales rep at AW Computing is unable to find what they are looking for While scrolling through their Chatter fee How can a filter be utilized to only posts from their key account and Opportunity records?
Answer : B
The correct answer is B. Create a Chatter stream.
A Chatter stream gives users a combined feed from selected people, groups, and records. Salesforce documentation states that users can create a Chatter stream to get a combined view of feeds from selected profiles, groups, and records.
For this requirement, the sales rep can create a stream that includes only the key Account and Opportunity records, so their Chatter feed is filtered to those important records.
Why others are incorrect:
A . Chatter bookmarks save individual posts, but they do not create a filtered feed.
C . Chatter notification alerts users, but it does not filter the feed.
D . Chatter group is for group collaboration, not filtering posts from selected records.
===========
Question 7
At Ursa Solar Major, only users with the Outer Planets profile Need to see the Jupiter field on the Solar System object. How should the app builder satisfy this requirement?
Answer : B
The correct answer is B. Field-level security.
Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.
Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.
All Official Question Types