Valid Sharing-and-Visibility-Architect Dumps shared by EduDump.com for Helping Passing Sharing-and-Visibility-Architect Exam! EduDump.com now offer the newest Sharing-and-Visibility-Architect exam dumps, the EduDump.com Sharing-and-Visibility-Architect exam questions have been updated and answers have been corrected get the newest EduDump.com Sharing-and-Visibility-Architect dumps with Test Engine here:
Universal Containers wants to create a way to store sensitive Invoice Data in Salesforce. A User who owns an Account should not see every Invoice, but only invoices that they or their subordinates own. Which two features should be considered during this solution implementation? Choose 2 answers.
Correct Answer: A,B
Explanation To store sensitive invoice data in Salesforce, the architect should consider using a master-detail relationship between accounts and invoices, and setting the organization-wide default sharing for invoices to private. This would ensure that only the owners of the invoices and their subordinates can see them, and that the invoices inherit the sharing settings of the accounts. A workflow that populates the invoice sharing object upon insert is not necessary if the master-detail relationship is used. A lookup relationship between accounts and invoices would not enforce the same level of security and visibility as a master-detail relationship3
Recent Comments (The most recent comments are at the top.)
Fa3il khayr - Jun 04, 2026
Answer is B and D
B. Ensure that the Organization-Wide Default sharing for Invoices is set to Private.
The requirement states that an Account owner should not automatically see every Invoice. Setting Invoice OWD to Private ensures that only the Invoice owner, their managers (through role hierarchy), and explicitly shared users can access Invoice records.
D. Deploy the Relationship between Accounts and the Invoices Object as Lookup.
A Lookup relationship allows the Invoice object to:
Have its own owner Have its own sharing model Be secured independently from the Account
This is essential because users should only see invoices that they or their subordinates own, regardless of Account ownership. In contrast, a Master-Detail relationship would inherit ownership and sharing from the Account.
IG: @mattch04 - Oct 14, 2024
A and B
"only invoices that they or **their** subordinates own". The user should have access to all the invoice detail records of the Parent. A lookup is not required.
It helps to look at it from the point of view of the Master not the detail owner.
Sky - Apr 16, 2024
B D A - is incorrect. Having ownership to account in Master detail relation to invoice will give access to all invoice records. Parent record dictates the ownership to child records. So its not A. C - is incorrect because workflow cannot create records other than tasks.
Russel - Mar 23, 2024
Answer would be B & D, Since account owner should not see all Invoice only which they or their subordinates own. Master detail will control by parent
Recent Comments (The most recent comments are at the top.)
Answer is B and D
B. Ensure that the Organization-Wide Default sharing for Invoices is set to Private.
The requirement states that an Account owner should not automatically see every Invoice. Setting Invoice OWD to Private ensures that only the Invoice owner, their managers (through role hierarchy), and explicitly shared users can access Invoice records.
D. Deploy the Relationship between Accounts and the Invoices Object as Lookup.
A Lookup relationship allows the Invoice object to:
Have its own owner
Have its own sharing model
Be secured independently from the Account
This is essential because users should only see invoices that they or their subordinates own, regardless of Account ownership. In contrast, a Master-Detail relationship would inherit ownership and sharing from the Account.
A and B
"only invoices that they or **their** subordinates own". The user should have access to all the invoice detail records of the Parent. A lookup is not required.
It helps to look at it from the point of view of the Master not the detail owner.
B D
A - is incorrect. Having ownership to account in Master detail relation to invoice will give access to all invoice records. Parent record dictates the ownership to child records. So its not A.
C - is incorrect because workflow cannot create records other than tasks.
Answer would be B & D, Since account owner should not see all Invoice only which they or their subordinates own.
Master detail will control by parent