Salesforce Certified Platform Sharing and Visibility Architect Practice Questions

Salesforce Certified Platform Sharing and Visibility Architect exam preparation

Salesforce Certified Platform Sharing and Visibility Architect practice questions in English: 180 questions with explanations. The mock exam has 60 questions and 120 minutes.

Salesforce Certified Platform Sharing and Visibility Architect free question 7 / 10 · Domain 2: Access to Records

When querying sharing rows, a developer finds a row whose RowCause is ImplicitChild (the Reason shown in the UI is Account Sharing). To remove this access from a particular user, the developer is considering deleting the row. Which statement matches the description of types of sharing in the Apex Developer Guide (Winter ’23)?

  1. Built-in implicit sharing cannot be changed directly from the UI, the SOAP API, or Apex
  2. The row can be removed from the Sharing button in the UI, but not from Apex or the API
  3. Running a DELETE statement in Apex with the RowCause specified can remove implicit sharing rows too
  4. The row can be removed through the SOAP API, but not from an Apex trigger
Show the answer and explanation

Answer: A

Why this is correct
In the description of managed sharing (record ownership, the role hierarchy, and sharing rules), the guide says: "All implicit sharing added by Force.com managed sharing cannot be altered directly using the Salesforce user interface, SOAP API, or Apex." Rows such as ImplicitChild and ImplicitParent are added by Salesforce on the basis of ownership or other sharing, and developers do not remove access by deleting them.

Why the other options are wrong
"Running a DELETE statement in Apex with the RowCause specified can remove implicit sharing rows too" … The guide lists Apex among the three ways in which implicit sharing added by managed sharing cannot be changed directly. A DELETE statement in Apex does not remove it.
"The row can be removed from the Sharing button in the UI, but not from Apex or the API" … The UI is not an exception either. The guide names the user interface, the SOAP API, and Apex together as ways that cannot alter implicit sharing directly.
"The row can be removed through the SOAP API, but not from an Apex trigger" … The SOAP API is one of the three ways the guide names as unable to alter implicit sharing directly. Changing the entry point does not make the row removable.

What to change instead
To take away access that implicit sharing has granted, change the ownership, sharing rule, or manual share that it is derived from. Code that edits share rows directly should stay with the manual shares and Apex managed shares that developers add themselves.

Go to the Salesforce Certified Platform Sharing and Visibility Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set