Question bank
Salesforce Certified Application Architect
40 Salesforce Certified Application Architect questions with the correct answer and a written explanation, organised across 4 exam domains.
- 40 questions
- 4 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Data Architecture
10 questions in this domain
- Question 1Single Choice
In Salesforce data modeling, which relationship type couples the child record’s lifecycle and security to its parent?
- ALookup
- BMaster-DetailCorrect answer
- CMany-to-Many
- DSelf Relationship
Why this is the answer
Master-Detail creates tight coupling, inherits sharing behavior, and causes cascade delete; Lookup keeps child records independent.
- Question 2Multiple Select
Which two statements correctly describe Organization-Wide Defaults (OWD) according to the playbook?
- AOWDs are the baseline access level for the most restrictive user.Correct answer
- BOWDs should be Private or Public Read Only to allow controlled expansion of access.Correct answer
- COWDs grant object access through sharing rules.
- DOWDs override the Role Hierarchy.
Why this is the answer
OWDs define a restrictive baseline; access is then expanded through Role Hierarchy and Sharing Rules while remaining scalable.
- Question 3Interactive
Review the SOQL query. Which relationship type is demonstrated by filtering on WhatId?
- AMaster-Detail
- BPolymorphicCorrect answer
- CLookup
- DSelf
Why this is the answer
WhatId is a polymorphic relationship field because it can reference several object types, enabling flexible data structures.
- Question 4Single Choice
When designing for Large Data Volumes, which feature stores frequently queried fields in a compact table to improve performance?
- ACustom Index
- BSkinny TablesCorrect answer
- CBig Objects
- DRoll-Up Summary
Why this is the answer
Skinny tables are a recognized LDV pattern that improves performance by storing frequently used fields in a smaller table.
- Question 5Multiple Select
Which two traps are specifically associated with large data volumes and query performance?
- AIndexing MisconceptionsCorrect answer
- BTreating Big Objects like standard objectsCorrect answer
- CTool Over-Usage Pitfall
- DIgnoring Data Locality
Why this is the answer
Indexing misconceptions and treating Big Objects like standard objects can cause performance issues at scale.
- Question 6Interactive
The code block creates a record in Salesforce. Which sharing mechanism is being used?
- AManual Sharing
- BApex Managed SharingCorrect answer
- CCriteria-Based Sharing Rule
- DRole Hierarchy
Why this is the answer
The code inserts an AccountShare record programmatically, which is Apex managed sharing.
- Question 7Single Choice
Which security principle grants users only the minimum access necessary to perform their job?
- APrinciple of Least PrivilegeCorrect answer
- BOrganization-Wide Defaults
- CRole Hierarchy
- DSharing Rules
Why this is the answer
Least privilege grants the minimum required access, reducing risk and preventing accidental data manipulation.
- Question 8Multiple Select
Which two statements correctly differentiate Role Hierarchy and Sharing Rules?
- ARole Hierarchy grants implicit vertical access to managers.Correct answer
- BSharing Rules provide horizontal access across branches.Correct answer
- CRole Hierarchy is always used for cross-functional collaboration.
- DSharing Rules enforce object-level security.
Why this is the answer
Role Hierarchy provides vertical access; Sharing Rules expand access horizontally across the hierarchy.
- Question 9Interactive
Based on the OWD configuration shown, what is the baseline access level for Account records?
- AAll users can edit all accounts
- BAccount records are only accessible to users who are explicitly granted accessCorrect answer
- CManagers automatically see all accounts
- DPublic users can read accounts
Why this is the answer
Private OWD is a restrictive baseline; access can only be expanded through explicit grants.
- Question 10Single Choice
Which data integration pattern is synchronous and waits for the receiving system to respond?
- ABatch Integration
- BRequest-ResponseCorrect answer
- CFire-and-Forget
- DData Virtualization
Why this is the answer
Request-Response is synchronous; the calling system waits for the target to respond before continuing.
Development Lifecycle
10 questions in this domain
- Question 11Single Choice
In Salesforce data modeling, which statement best explains the primary functional difference between a Master-Detail relationship and a Lookup relationship?
- AIt prevents all record deletion.
- BIt controls ownership, sharing, and deletion behavior.Correct answer
- CIt allows multiple parents of different types.
- DIt only affects page layouts.
Why this is the answer
Master-Detail creates tight coupling where the parent controls ownership, security, and cascade delete; Lookup leaves records independent.
- Question 12Multiple Select
Which two of the following characteristics accurately describe a Master-Detail relationship in the Salesforce data model?
- ARoll-up summary fields are availableCorrect answer
- BChildren can be orphaned if parent is deleted
- CChild records inherit the parent's sharing modelCorrect answer
- DRecords can have multiple parent records
Why this is the answer
Master-Detail supports roll-up summaries and makes child security dependent on the parent, but it prevents orphaned children and assumes one parent.
- Question 13Interactive
The code block defines a custom relationship field. What is true about this relationship type?
- AChild records inherit security and deletion behavior from the parent.Correct answer
- BThe child is independent and can be deleted separately.
- CThe field allows for multiple parent objects.
- DThe relationship creates a many-to-many junction.
Why this is the answer
The field type is MasterDetail, so the parent controls security and deletion. Child records cannot be orphaned and do not have independent access.
- Question 14Single Choice
Why might a Salesforce architect intentionally choose denormalization even though it adds some data redundancy?
- ATo increase data redundancy and storage costs
- BTo improve user experience and reporting simplicityCorrect answer
- CTo avoid using lookup relationships
- DTo enforce stricter field-level security
Why this is the answer
Denormalization is often used to improve reporting ease and user experience by reducing complex joins and making data easier to consume.
- Question 15Multiple Select
Which two tactics help architects manage Large Data Volumes in Salesforce effectively?
- AUse skinny tablesCorrect answer
- BArchive historical dataCorrect answer
- CIndex every custom field
- DStore all data in standard objects
Why this is the answer
Skinny tables and archiving help optimize performance in LDV environments, while excessive indexing and forcing data into standard objects are not reliable strategies.
- Question 16Interactive
The code block shows a SOQL query. Which factor most directly impacts its performance in an LDV org?
- ANumber of fields in the SELECT clause
- BWhether the filter field is indexedCorrect answer
- CUse of a bind variable
- DLength of the object API name
Why this is the answer
Selectivity and indexes determine query performance in high-volume orgs; bind variables and field selection are secondary.
- Question 17Single Choice
What is a polymorphic relationship in the Salesforce data model?
- AA relationship that relates one record to multiple target object typesCorrect answer
- BA relationship with multiple parent records on one child
- CA lookup field pointing to a single object
- DA many-to-many relationship implemented by a junction object
Why this is the answer
Polymorphic relationships allow a single object to relate to multiple object types, such as WhatId or WhoId on tasks and events.
- Question 18Multiple Select
Which two risks are caused by over-modeling the Salesforce data schema with too many small objects?
- AComplex joins and performance degradationCorrect answer
- BExcessive data fragmentation across many objectsCorrect answer
- CCluttered page layouts with too many fields
- DHitting the object field limit
Why this is the answer
Over-modeling increases the number of joins and fragments data, causing query complexity and performance issues. Layout clutter and field limits come from under-modeling.
- Question 19Interactive
The code block shows a profile and an assigned permission set. What is the user's effective Account access?
- ARead only
- BEditCorrect answer
- CNo access
- DView All but not Edit
Why this is the answer
Permission sets are additive. Adding Edit on Account grants the user edit access, which includes read access in Salesforce.
- Question 20Single Choice
Which statement best describes the Principle of Least Privilege in a Salesforce architecture?
- AGrant users the minimum access required for their roleCorrect answer
- BGrant all access through the Role Hierarchy
- CUse Profiles to maximize object permissions
- DShare records with all internal users
Why this is the answer
Least privilege minimizes the blast radius of credential compromise and prevents accidental data manipulation by granting only required access.
Identity and Access Management
10 questions in this domain
- Question 21Single Choice
Based on the playbook, what does the Principle of Least Privilege require in an identity architecture?
- AGrant every user full object access
- BGrant the minimum access needed for the roleCorrect answer
- CGrant access only to System Administrators
- DGrant access based on data volume
Why this is the answer
Least privilege means users receive only the minimum access required for their job, limiting the impact of compromised credentials.
- Question 22Multiple Select
Based on the playbook, which statements correctly distinguish object-level security from record-level security? Select all that apply.
- AObject security controls which records are visible
- BRecord-level sharing cannot override missing object accessCorrect answer
- CUsers need both layers to see a recordCorrect answer
- DSharing rules can override object-level deny
Why this is the answer
Object-level security defines what objects and fields are available; record-level security defines which records are visible. Both layers must allow access.
- Question 23Interactive
Based on the sharing configuration in the code block, what is the baseline access for Account records?
- APublic Read Only
- BPrivateCorrect answer
- CPublic Read/Write
- DControlled by Parent
Why this is the answer
OWDs establish the most restrictive baseline; Private is the most restrictive Account default, while Role Hierarchy and sharing rules can expand access.
- Question 24Single Choice
Based on the playbook, what is the purpose of Organization-Wide Defaults in the sharing model?
- ADefine the most restrictive baselineCorrect answer
- BGrant access through manual sharing
- CReplace all profile permissions
- DStore field-level security settings
Why this is the answer
Organization-Wide Defaults represent the baseline level of access for the most restrictive user, and other mechanisms expand from that baseline.
- Question 25Multiple Select
Based on the playbook, which statements about Role Hierarchy and Sharing Rules are true? Select all that apply.
- ARole Hierarchy gives managers access to subordinatesCorrect answer
- BSharing Rules provide access across hierarchy branchesCorrect answer
- CRole Hierarchy should grant all horizontal access
- DSharing Rules only restrict access
Why this is the answer
Role Hierarchy supports vertical access, while Sharing Rules provide horizontal access. Overusing the hierarchy for all sharing creates hierarchy bloat.
- Question 26Interactive
Based on the configuration in the code block, why is this an appropriate scalable access model?
- AIt keeps Profiles slim and uses Permission SetsCorrect answer
- BIt places all permissions in the Profile
- CIt removes the need for sharing rules
- DIt grants every user the same profile
Why this is the answer
Modern architecture keeps Profiles minimal and grants additive access through Permission Sets, especially Permission Set Groups, for scalability.
- Question 27Single Choice
Based on the playbook, why is manual sharing always considered technical debt in high-volume architectures?
- AIt does not scale with dynamic access or volumeCorrect answer
- BIt is not a valid sharing mechanism
- CIt automatically removes record access
- DIt requires no maintenance
Why this is the answer
Manual sharing does not scale with dynamic business logic and data volume, making it technical debt in large architectures.
- Question 28Multiple Select
Based on the playbook, which mechanisms support automated sharing in a scalable architecture? Select all that apply.
- ACriteria-Based Sharing RulesCorrect answer
- BApex Managed SharingCorrect answer
- CManual sharing per record
- DBroad Profile permissions
Why this is the answer
Criteria-Based Sharing Rules and Apex Managed Sharing automate access at scale, while manual sharing and broad profiles create technical debt.
- Question 29Interactive
Based on the access levels in the code block, what effective access does the user have to the field?
- ARead/Write
- BRead Only
- CNo accessCorrect answer
- DFull access
Why this is the answer
The most restrictive rule applies; field-level deny overrides record access, so the user cannot see the field.
- Question 30Single Choice
Based on the playbook, how should Profiles and Permission Sets be used in modern architecture?
- AProfiles stay slim; Permission Sets add accessCorrect answer
- BPermission Sets replace all profiles
- CProfiles are used to define sharing rules
- DPermission Sets cannot contain object permissions
Why this is the answer
Profiles should contain baseline permissions, and Permission Sets should add access to support scalability and least privilege.
Integration Architecture
10 questions in this domain
- Question 31Single Choice
Which relationship type creates a tight coupling between records, affecting security and record lifecycle within the data model?
- AMaster-DetailCorrect answer
- BLookup
- CMany-to-Many
- DPolymorphic
Why this is the answer
Master-Detail creates a tight coupling that affects sharing and record deletion. Lookup remains loose and does not control child record lifecycle or security.
- Question 32Multiple Select
Which two characteristics belong to a Master-Detail relationship type in the Salesforce data model when compared to a Lookup relationship?
- AParent deletion cascades to child recordsCorrect answer
- BRoll-up summaries are available on the masterCorrect answer
- CChild records have independent sharing
- DRecords can be reparented without restriction
Why this is the answer
Master-Detail relationships support roll-up summaries and cascade deletes. Children inherit sharing behavior and reparenting is restricted, so those options are false.
- Question 33Interactive
Based on the schema, what automatically happens when a Project__c record is deleted?
- AThey are deleted with the projectCorrect answer
- BThey remain as orphans
- CThey are assigned to a default project
- DThey are converted to Task records
Why this is the answer
Because Project_Task__c is a Detail in a Master-Detail relationship, deleting the Project__c master automatically deletes all related Project_Task__c records.
- Question 34Single Choice
What does a polymorphic relationship allow a record to do in the Salesforce data model?
- ARelate one object to multiple object typesCorrect answer
- BRelate multiple records to one field
- CCreate a private sharing model
- DAggregate data without queries
Why this is the answer
Polymorphic relationships, such as WhatId and WhoId, allow a single object to relate to several different object types within one unified interface.
- Question 35Multiple Select
Which two examples use polymorphic relationships, such as those found on Task and Event records in Salesforce?
- ATask WhatId pointing to Account or OpportunityCorrect answer
- BEvent WhoId pointing to Lead or ContactCorrect answer
- CMaster-Detail from Opportunity to Account
- DBig Object storing archived events
Why this is the answer
Task and Event use polymorphic WhatId and WhoId fields to reference different object types. A Master-Detail is fixed, and Big Objects are for storage, not polymorphic relationships.
- Question 36Interactive
Under high-concurrency updates, what risk does this roll-up summary design introduce?
- ARow locking on the parent Account__cCorrect answer
- BNon-selective SOQL queries
- CLoss of field-level security
- DOrphaned child records
Why this is the answer
Roll-up summary recalculations update the parent record, so frequent child updates can cause row-locking contention on the parent in high-volume environments.
- Question 37Single Choice
What is a recommended element of a Large Data Volume strategy in Salesforce when designing for scale?
- AUsing skinny tables and indexingCorrect answer
- BMaking every object private
- CStoring all data in one object
- DUsing manual sharing everywhere
Why this is the answer
LDV strategies rely on skinny tables, selective indexes, archiving, and off-platform storage to maintain query performance and avoid locking issues.
- Question 38Multiple Select
Which two strategies are part of a Large Data Volume architecture when managing millions of records in Salesforce?
- AUsing index-aware query designCorrect answer
- BPlanning archiving or off-platform storageCorrect answer
- CAdding every field to a custom index
- DPlacing all records in a Big Object
Why this is the answer
Index-aware queries and archiving/off-platform storage are LDV best practices. Excessive custom indexes hurt DML performance, and Big Objects are not a universal replacement.
- Question 39Interactive
Why could this SOQL query cause a timeout in a large production org when the Account table contains millions of rows?
- ALeading wildcard makes the query non-selectiveCorrect answer
- BCustom fields always time out in SOQL
- CAccount object cannot be queried in bulk
- DRecord type is not included in the query
Why this is the answer
A leading wildcard in LIKE makes the query non-selective, preventing efficient index usage and causing expensive full scans at scale.
- Question 40Single Choice
What is the purpose of Master Data Management in an architecture that spans multiple systems and needs a reliable source?
- AA single authoritative source of truthCorrect answer
- BA backup of all records in Salesforce
- CA custom object for every business entity
- DAn index for every field in the org
Why this is the answer
MDM establishes one trusted source for critical entities like Account or Contact and defines whether Salesforce is the system of record or a consumer.
Frequently asked questions
Everything about the Salesforce Certified Application Architect question bank and how to use it.