Understanding the Effects of "Controlled by Parent" Organization-Wide Default

Correct Answer: B and C

When the organization-wide default is set to be controlled by the parent, the access of the records is determined by the user's access to the parent record.

In addition to this, sharing rules are not available for the object.

Option A is incorrect because sharing rules are not available for objects that have organization-wide default controlled by the parent.

Option D is incorrect because permission sets provide access to objects, not records.

References:

Correct Answer: B and C

When the organization-wide default is set to be controlled by the parent, the access of the records is determined by the user's access to the parent record.

In addition to this, sharing rules are not available for the object.

Option A is incorrect because sharing rules are not available for objects that have organization-wide default controlled by the parent.

Option D is incorrect because permission sets provide access to objects, not records.

References:

Correct Answer: B and C

When the organization-wide default is set to be controlled by the parent, the access of the records is determined by the user's access to the parent record.

In addition to this, sharing rules are not available for the object.

Option A is incorrect because sharing rules are not available for objects that have organization-wide default controlled by the parent.

Option D is incorrect because permission sets provide access to objects, not records.

References:

When the organization-wide default of an object is set to be controlled by the parent, it means that the access to the records of that object is determined through the user's access to the parent record.

For example, if the organization-wide default of the Opportunity object is set to Controlled by Parent, then the user's access to each Opportunity record is determined by their access to the parent Account or Opportunity record.

If a user has read access to an Account or Opportunity record, they will also have read access to all the child Opportunity records. If the user does not have access to the parent record, they will not have access to any of the child Opportunity records.

This setting applies to all child records of the object, including related lists, lookup fields, and related records.

In this scenario, Sharing Rules are not available for the object, as the access to the records is already determined through the parent record.

Permission sets can still be used to grant additional access to specific records or fields, but the organization-wide default settings will still apply.

Overall, setting the organization-wide default of an object to Controlled by Parent is a way to ensure that users can only access records that are relevant to them, based on their access to the parent record.