The correct answer is B, based on the intended Salesforce wording.
In a private data model, users normally access records they own or records shared with them. Salesforce role hierarchy opens record access upward: users higher in the hierarchy can view, edit, and report on records owned by users below them, depending on object permissions and hierarchy settings.
Because the Service Coordinator needs access to work orders and related records owned by technicians, placing the SC above the technicians in the role hierarchy gives the required record access without granting excessive org-wide permissions.
Why others are incorrect:
Modify All Data is too broad.
Modify All on Work Order only applies to that object and does not solve access to other related technician- owned records.
Workflow does not grant record access.

The correct answer is B. The deployed permission set will only contain changes related to the change set.
When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.
A is incorrect because the whole permission set is not simply wiped and replaced.
C is incorrect because field-level security can be deployed when included properly.
D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

The correct answer is D. Universal Containers wants the real-time value of the Account's Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.
Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce's TEXT function supports picklist values in formulas.
Example formula concept:
TEXT(Account.Support_Level__c)
Why others are incorrect:
A is incorrect because the formula must be on Case, not Account.
B is incorrect because Case already relates to Account; a new lookup alone does not display the value.
C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

For an unmanaged package, Salesforce documentation states that the developer who created and uploaded the package has no control over installed components and can't change or upgrade them after installation.
Therefore, an unmanaged package does not follow the normal managed-package upgrade path. To get a newer version, the practical process is to remove the installed unmanaged package and install the newer version.
Why others are incorrect:
B and D describe managed/update-style behavior, not unmanaged package behavior.
C is not the package upgrade process itself; it describes a deployment workaround, not upgrading the installed unmanaged package.

The correct answers are A. Create a master-detail relationship field on Application to Open_Position and B). Create a master-detail relationship field on Application to Job Candidate .
This requirement describes a many-to-many relationship : one Job Candidate can apply for multiple Open Positions, and one Open Position can have multiple Job Candidates. The correct Salesforce design is to use a junction object , which in this case is Application__c .
Salesforce documentation states that many-to-many relationships can be modeled using master-detail relationships between a junction object and the two related objects.
So Application__c should have:
* A master-detail relationship to Job_Candidate__c
* A master-detail relationship to Open_Position__c
This allows applications to appear on the Job Candidate record and also on the Open Position record.
C and D are incorrect because the relationship fields should be created on the junction object , Application__c , not from the parent objects back to Application.