Application Performance & Scalability Flashcards
7 cards from real SAA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Application Performance & Scalability flashcards as text
Which approach should an architect recommend to allow external systems to upsert Salesforce records without knowing internal Salesforce IDs?
Answer: Define an External ID field on the object
External ID fields allow external systems to use their own identifiers for upsert operations, enabling idempotent integrations without needing Salesforce-generated IDs.
A Visualforce page is experiencing slow load times due to excessive view state. What is the maximum allowed view state size?
Answer: 128 KB
Visualforce view state is capped at 135 KB (often cited as 128 KB threshold for practical purposes); exceeding it causes errors and requires reducing data stored in state.
What is the primary advantage of using Queueable Apex over Future Methods?
Answer: Queueable Apex supports chaining and can accept non-primitive parameters
Queueable Apex supports job chaining (enqueueing another job from within a job) and accepts complex object types as parameters, making it more flexible than Future Methods.
In a Large Data Volume environment, which index type must Salesforce Support enable, as it is not available through Setup by default?
Answer: Custom Index
Custom Indexes are created by Salesforce Support upon request and are applied to fields that need to be indexed to improve query selectivity on high-volume objects.
Platform Events in Salesforce are primarily used to improve scalability by enabling which architectural pattern?
Answer: Event-driven architecture with decoupled producers and consumers
Platform Events implement an event-driven publish/subscribe model that decouples systems, allowing producers to publish events without waiting for consumers, improving throughput and resilience.
When should an architect choose SOSL (Salesforce Object Search Language) over SOQL for a use case?
Answer: When searching for a term across multiple objects and fields simultaneously
SOSL is optimized for full-text search across multiple objects and fields at once, leveraging Salesforce's search index rather than performing per-object SOQL queries.
A custom object has 10 million records and queries are timing out. Salesforce Support confirms the WHERE clause field is indexed. What should the architect investigate next?
Answer: Check if the query is non-selective due to too many matching records (>10% of total)
Even indexed fields become non-selective if the query matches more than roughly 10% of total records, causing Salesforce to fall back to a full table scan and ignore the index.