Exam Certified Platform App Builder topic 1 question 444 discussion

"Read permission and read access to the related master record. If the record has two master records in a many-to-many relationship, the user must have read access to both master records." Can check this documents: https://help.salesforce.com/s/articleView?id=platform.dev_security.htm&type=5

the question is stupid, we cannot configure or remove read access from either object once we are creating master detail relationship. thats an inbuild functionality. automatically it will have read access on both objects

C is the correct option

C is correct option. User profile level, you can select read access for junction object only when u have read access of both master objects. User only can access junction obj record, if user profile has read access on junction obj. Tested, working.

B, You only need permission for one master object to "view Request Inventory records". This question is testing that specific knowledge.

Its C https://salesforce.stackexchange.com/questions/65250/visibility-of-records-in-a-junction-object-and-based-or-relationshiporder-base https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5 TLDR; you need access to both masters to have the same access to the Junction

I think the same, A and D are definitely wrong, B. works but C. is also right so...not sure which one is considered the correct one. My choice is B because read access on the first master-detail relationship is enough to have access to the junction object.

A doesn't make sence to me. D is wrong, because Custom Objects controlled by parent ( detail in Master Detail relationship) can not have sharing rule. B I've tested and it works. C I think it's obvious that it will work also with Read access to both master objects.

D. The app builder needs to provide sharing rules on the Request Inventory object because it is the junction object in a many-to-many relationship between the Inventory and Order objects. Sharing rules determine the level of visibility users have to the Request Inventory records, such as read or edit access. Without sharing rules on the Request Inventory object, users may not be able to view or interact with the Request Inventory records, which would hinder their ability to track orders against inventory and fulfill order requests. By setting appropriate sharing rules, the app builder can ensure that users have the necessary access to the Request Inventory records to carry out their responsibilities and achieve the desired business outcome.