Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. SHARING-AND-VISIBILITY-ARCHITECT

Salesforce SHARING-AND-VISIBILITY-ARCHITECT Exam
Salesforce Certified Sharing and Visibility Architect (Page 25 )

Updated On: 7-Feb-2026
Page 8 of 44
PDF with 240 Questions

Universal Containers (UC) has created a public group with certain Sales Engineers to help on complex deals and a sharing rule to grant access to these opportunities. Opportunity OWD is private.

What is the impact of these sharing settings?

  1. Subordinates of Managers who have Sales Engineers in the public group will also have access to these records.
  2. Sales Engineers that have a similar role of the Sales Engineers of the public group will also have access to these records.
  3. Sales Engineers Managersand their managers in the role hierarchy will also have access to these records.
  4. Sales Engineers direct reports will also have access to these records.

Answer(s): C



Jane, a support representative at Universal Containers, created a report to view all her open

cases that have been created in the past 7 days and saved the report in the "Private Reports" folder.

Who can view and run the report?

  1. The report owner and any users who have been given access to the "My Private Reports" folder
  2. The report owner and anybody in the role hierarchy above the report owner
  3. The report owner
  4. The report owner and users with the "View All Data" permission

Answer(s): C



Universal Containers (UC) stores basic employee information in a custom Employee object (OWD -

Public Read Only). There are a few sensitive fields that need restricted access (salary,
grade

level, last performance rating).

Other than field level security, what other options are available to make these fields

accessible to the Human Resource team?

  1. Create a new custom object controlled by parent and a Master-Detail relationship to Employee to store new restricted information.
  2. Change OWD of Employee custom object to private and a Lookup self-relationship to store only new restricted information.
  3. Create a new custom object with private OWD and Lookup relationship to Employee to store new restricted information.
  4. There are no other options besides using field level security.

Answer(s): C



A sales rep (John) at Universal Containers (UC) requested to update information in an

account record where he has READ only access. John requested the EDIT access permission

from the owner of the record (Paul). Paul manually shared the record with John. Assuming the

OWD of the Account object is Public Read-Only, what is the impact in the system?

  1. New AccountShare record is created. Row Cause is "Manual" and Access Level is "Read/Write".
  2. Existing AccountShare record is updated. Row Cause is "Owner" and User/Group is "John".
  3. New AccountShare record is created. Row Cause is "Owner" and Access Level is "Full".
  4. Existing AccountShare record is updated. Row Cause is "Manual" and Access Level is "Read/Write".

Answer(s): A



The Finance team at Universal Containers usually does not need access to Account and
Contract records A .. given Opportunity access for a big deal to help with tax calculation.
She can now also access Account and C..

Whichtwo reasons could be causing this issue? Choose 2 answers

  1. Contact records can be accessed due to implicit sharing from Account.
  2. Account records can be accessed due to implicit sharing from Opportunity.
  3. Contact records can be accessed due to implicit sharing from Opportunity.
  4. Account records can be access due to role hierarchy.

Answer(s): A,B






Post your Comments and Discuss Salesforce SHARING-AND-VISIBILITY-ARCHITECT exam prep with other Community members:

Join the SHARING-AND-VISIBILITY-ARCHITECT Discussion