<< Prev Question Next Question >>

Question 22/109

Universal Containers (UC) has recently changed its internal policy to follow market regulations and create an internal team to manage the collection process. Only this team should have access to Invoke records. currently, invoke is a child in a Master-Detail relationship to Account. Although related lists have been removed from the page layouts, some profiles stills have access to the invoice object.
Which approach should an architect recommend to fix this problem?

A. Change the Invoke organization-wide default from Controlled by Parent to Private and remove invoke access from the unauthorized

B. Create a Permission Set with No Access to the Invoice object and assign it to unauthorized users.

C. Create a new Profile with no access to the Invoice object and assign it to all unauthorized users.

D. Replace Account and Invoke Master Detail Relationship by a Lookup and remove Invoice Access from the unauthorized profiles,

Recent Comments (The most recent comments are at the top.)

Gina - Jan 15, 2024

Ans: D

Bob_M - Nov 28, 2023

A - can't change for a Detail in Maser-Detail relationship
B - no point, they already have access. Would be a good option if it said "remove access from permset"
C - Will work only if there are also no permsets assigned, and also too much work for just one object permission =)
D - Fits all needs: "Only this team should have access to Invoke records" and "some profiles stills have access to the invoice object", so, changing to Lookup to make OWD Private and removing Profile object-level access

AbtTkExam - Oct 07, 2023

D is correct ans

Vladyslav - Sep 04, 2023

D - only correct option

Question 22/109

Recent Comments (The most recent comments are at the top.)

LEAVE A REPLY

Download PDF File