At Kalgoorlie Analytics, the organisation-wide default for the Contract object is Public Read Only. The compliance team, defined as a public group, must be able to edit every Contract record regardless of owner, but no other change to the baseline is wanted. Which configuration achieves this with the least disruption?
- ACreate an owner-based sharing rule that shares Contract records owned by all internal users with the compliance public group at Read/Write access level. Correct
- BChange the Contract organisation-wide default to Public Read/Write so that everyone, including the compliance group, can edit all Contract records without further configuration.
- CCreate a criteria-based sharing rule on Contract that shares all records with the compliance public group at Read/Write access level.
- DAssign the compliance group members a permission set with the Modify All permission for the Contract object, which grants edit access to all Contract records.
Why A is correct: Correct. An owner-based sharing rule keyed on records owned by all internal users grants the compliance group Read/Write across every record while leaving the Public Read Only baseline untouched for everyone else.
Why B is wrong: Tempting because it guarantees the compliance team can edit, but it grants edit access to the entire organisation, which contradicts the requirement to change nothing else about the baseline.
Why C is wrong: Tempting because sharing rules can grant Read/Write, but a criteria-based rule keys off field values on the record; with no meaningful criterion to match every record this is the wrong sharing-rule type for an all-records share.
Why D is wrong: Tempting because Modify All on an object does grant edit to all its records, but it also bypasses sharing entirely and is a broad object permission rather than the targeted record-sharing the requirement calls for; it cannot be assigned to a public group, only to profiles or permission sets per user.