The correct answers are A. There are already two master-detail relationships on the Invoice Line Item and C. Invoice Line Item records exist without having the Invoice lookup field populated.

Salesforce allows a lookup relationship to be converted to a master-detail relationship only when the lookup field has a value on all existing records. Therefore, if any Invoice_Line_Item__c records do not have the Invoice lookup populated, Salesforce prevents the conversion.

Salesforce also limits each custom object to up to two master-detail relationships. If Invoice Line Item already has two master-detail relationships, it cannot have another master-detail relationship added or converted.

B is incorrect because custom objects can be on the detail side of master-detail relationships. D is incorrect because a roll-up summary field on Invoice is not the reason this lookup-to-master-detail conversion would be blocked.

===========

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.

The correct answers are A. Tabular format and B. Summary format.

Salesforce reporting snapshots can use custom tabular or summary reports as the source report. Salesforce documentation specifically states that a reporting snapshot source report can be tabular or summary.

Why others are incorrect:

C. Joined format is not supported as a reporting snapshot source report.

D. Matrix format is not supported because matrix reports group by rows and columns, and Salesforce troubleshooting guidance states that matrix reports can’t be used with reporting snapshots.

===========

The correct answer is A. Partial Copy.

A sandbox template is used to define which object data is copied into a sandbox. Salesforce documentation states that sandbox templates control what data is copied into Full or Partial Copy sandboxes. Since the question says the app builder created a sandbox template for Accounts, Projects, and Project Milestones, the correct testing environment is Partial Copy because it includes metadata plus a selected sample of production data defined by the sandbox template. Developer, Developer Pro, and Scratch Orgs do not use sandbox templates for selected production data in this way.

===========

The correct answers are A. Review the Contact record and ensure it is linked to an Account, C. Verify the users with the issue have access to the Contact object, and E. Confirm whether Default Organization-Wide Sharing Settings provide access to the Account.

A Contact that is not linked to an Account is treated as a private contact. Salesforce states that contacts without an account are private regardless of the sharing model, so checking whether the Contact is associated with an Account is a valid troubleshooting step.

Users also need object-level access to the Contact object. Object permissions control whether users have base-level access such as read, create, edit, and delete for an object.

Finally, Contact visibility is often affected by Account access, especially when Contact sharing is controlled by the parent Account. Organization-Wide Defaults define the default record access users have for records they do not own, so checking the Account OWD is also correct.

B is incorrect because creating a new Contact does not troubleshoot the actual sharing/security issue.

D is incorrect because creating a broad Account Sharing Rule for all records is not the first troubleshooting step and may overexpose data.

===========

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

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.

A utility bar gives users quick access to commonly used productivity tools and components from within a Lightning app or console app. Salesforce describes the utility bar as a fixed footer that provides fast access to tools such as Notes, History, softphone, flows, and custom utilities. Utilities open in docked panels, allowing users to keep working without leaving the current page. This exactly matches the requirement: components accessible from anywhere in the app without leaving the page.

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.

===========

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.

===========