A new field has been added to the Applicant object that is part of an unmanaged package. A recruiter ran the Position with or without Applicants report and noticed that the new field was missing as an option to add as a column.
How should an app builder troubleshoot this issue?

Universal Containers has a private sharing model for Accounts and Opportunities and uses Territory Management to grant access to records.
* Sales rep A manually shares an opportunity record with sales rep B.
* Sales rep B has access to the Account even though the Account Is NOT In sales rep B's territory.
* Sales rep C CANNOT see either record.
Based on the information given, why can sales rep B see the Account related to the Opportunity?

An App Builder is loading the data into salesforce. To link the new records back to the legacy system, a field will be used to track the legacy ID on the account object. For future data loads this ID will be used when upserting records. Which field attribute should be selected? Choose 2 answers

At Universal containers, all US Sales reps should be able to view the US Team dashboard, however, only the US sales directors should be able to see the data in the component and view its source report. How can an app builder ensure the proper access is granted?

Universal Containers has two types of applicants, hourly and salary. There are separate record types for each. While all members of the human resource department need to be able to view all applicant records, only the hiring Manager and VP of HR should be able to create salary applicant records.
What should the app builder recommend to meet this requirement?