Salesforce Certified Application Architect Free Sample Questions

Data Architecture and Management · Large Data Volume Considerations

1. A

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

2. B

   Ownership Skew; Assign the 'System User' account to a user in the highest role of the hierarchy to bypass sharing calculations.

3. C

   Lookup Skew; Change the relationship between Transaction__c and Account from Master-Detail to Lookup to reduce locking contention.

4. D

   Ownership Skew; Remove the 'System User' from the Role Hierarchy entirely.

Sharing and Visibility · Declarative Sharing

1. A

   Set OWD to Public Read Only and use a Criteria-Based Sharing Rule to grant Write access for Critical status.

2. B

   Use Apex Managed Sharing to calculate access based on the Status field triggers.

3. C

   Set OWD to Private, keep 'Grant Access Using Hierarchies' enabled, and use a Permission Set to restrict access to non-Critical records.

4. D

   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'.

Data Architecture and Management · Data Modeling

1. A

   Lookup relationships determine the ownership of the child record, effectively inheriting the parent's owner.

2. B

   In a Master-Detail relationship, the security settings of the detail record are controlled by the master record.

3. C

   Lookup relationships are required if you need to create a Junction Object for many-to-many relationships.

4. D

   Master-Detail relationships allow the child record to have a different owner than the parent record.

5. E

   Master-Detail relationships allow for Roll-up Summary fields on the parent object, whereas Lookups do not support declarative Roll-ups.

Sharing and Visibility · Platform Encryption

1. A

   True

2. B

   False

Sharing and Visibility · Programmatic Sharing

1. A

   Use a Record-Triggered Flow to evaluate the complex criteria and add the user to the 'Shipment__Share' object.

2. B

   Create a scheduled Apex job that iterates over all Shipments and manually inserts Share records into the 'Shipment__Share' object using a standard 'Manual' RowCause.

3. C

   Create a 'Regional_Manager_Group' for each combination and use 50+ Criteria-Based Sharing Rules.

4. D

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

Data Architecture and Management · Data Integration

1. A

   Custom Object with a nightly Batch Apex interface

2. B

   Salesforce Big Objects

3. C

   Salesforce Connect with External Objects

4. D

   Heroku Connect with Postgres