At Universal Containers, Accounts and Contacts are normally visible to all employees, and Proposals (custom object) are visible to the Account owner and managers. However, some Proposals are considered confidential and are managed by a Strategic Proposals team. These Proposals should not be visible to anyone in the Sales group other than the owner and the strategic team.
How should the architect design for this requirement?

Universal Containers (UC) wants all full-time internal employees to be able to view all leads.
A subset of Contractors and temporary employees should also be able to see leads. Which organization-wide default (OWD) approach should an architect recommend that will help UC implement these requirements?

Universal Containers has created a custom object to store highly confidential client relationship data with Private sharing settings. Which two options would an Architect choose to ensure access only to the record owner and the administrator?
Choose 2 answers.

There is a custom object, Job, that has OWD set to "Private". It contains extremely private information that should only be available to the record owner and the hiring manager that is associated through a user Lookup field on the object.
What is the best solution to grant access?

Universal Containers has a requirement to share Accounts automatically to the users at a field office. They currently have the following setup in their environment:
Accounts are set to Private in the Org-Wide Default.
The field office is specified by a lookup in the account object.
There are 400 field offices.
The users in each field office are managed using public groups.
Based upon a lookup relationship field on the Account, how should the Architect meet their requirement?