Free App-Arch-301 sample questions

Correct answer: Account Data Skew; Redistribute the child Transaction__c records across multiple dummy accounts to ensure no single account exceeds 10,000 child records.

The scenario describes Account Data Skew, where a single parent record (Account) has more than 10,000 child records. This causes performance issues during sharing recalculations and record locking. The optimal solution is to distribute the child records across multiple parent accounts to mitigate the skew.

Correct answer: Set OWD to Private, disable 'Grant Access Using Hierarchies', and create a Criteria-Based Sharing Rule sharing records owned by 'Nurse' role with 'Care_Coordinator' role when Status is 'Critical'.

To strictly control access based on field criteria and prevent automatic vertical access, 'Grant Access Using Hierarchies' must be disabled for the custom object. A Criteria-Based Sharing Rule is then the most specific way to grant Read/Write access only when the status condition is met.

Correct answers: Master-Detail relationships allow for Roll-up Summary fields on the parent object, whereas Lookups do not support declarative Roll-ups.; In a Master-Detail relationship, the security settings of the detail record are controlled by the master record.

Master-Detail relationships uniquely support declarative Roll-up Summary fields to aggregate data from child records.

This is a key security distinction; detail records in a Master-Detail relationship inherit the sharing and security settings of their master parent.

Correct answer: True

Deterministic encryption allows for exact match filtering (group by, filter, sort) because the same plaintext always encrypts to the same ciphertext. Probabilistic encryption generates different ciphertext for the same plaintext each time, making filtering impossible.

Correct answer: Implement Apex Managed Sharing by creating a custom Apex Sharing Reason and inserting records into 'Shipment__Share' using triggers on the Shipment object.

Apex Managed Sharing (using a custom RowCause) is the correct architectural approach. It ensures that the sharing records are maintained by the system (not deleted upon record owner change) and allows for handling complex logic that exceeds declarative limits. It is more robust than manual sharing via Apex.

Correct answer: Salesforce Connect with External Objects

Salesforce Connect allows you to define External Objects that map to data stored outside Salesforce. These objects can be related to standard objects (like Account) via Indirect or External Lookups and displayed in related lists, meeting the requirement of viewing without physical storage.