Practice Test Geeks(SAA) Salesforce Application Architect Certification Practice Test
← All SAA Flashcard Decks

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

  1. What is the maximum number of SOQL queries allowed per Apex transaction in Salesforce?

    Answer: 100

    Salesforce enforces a governor limit of 100 SOQL queries per synchronous Apex transaction.

  2. Which Salesforce feature creates a separate, leaner copy of a large object table to improve query performance?

    Answer: Skinny Tables

    Skinny tables are Salesforce-maintained copies of standard or custom object tables that include only frequently queried fields, significantly improving read performance on large data volumes.

  3. An Apex transaction needs to process 500,000 records nightly. Which Apex pattern is most appropriate?

    Answer: Batch Apex

    Batch Apex is designed for processing large volumes of records by breaking them into manageable chunks, each with its own governor limit context.

  4. What is the recommended optimal batch size when using Batch Apex to avoid SOQL row limit errors while maximizing throughput?

    Answer: 200

    A batch size of 200 is the default and generally optimal, balancing governor limits (such as 50,000 SOQL rows) against processing efficiency.

  5. Which Salesforce feature allows caching of frequently accessed data at the org, session, or partition level to reduce repeated database queries?

    Answer: Platform Cache

    Platform Cache provides a dedicated caching layer in Salesforce at org or session scope, reducing redundant SOQL queries and improving application performance.

  6. A SOQL query is considered 'selective' when it uses indexed fields in the WHERE clause. Why is selectivity critical for Large Data Volume orgs?

    Answer: It prevents full table scans that degrade query performance

    Selective queries allow Salesforce to use indexes to retrieve a small subset of records, avoiding costly full table scans that become exponentially slower as data volume grows.

  7. What is the maximum CPU time limit per Apex transaction in synchronous contexts?

    Answer: 10,000 ms

    Salesforce enforces a 10,000 ms (10-second) CPU time limit for synchronous Apex transactions to ensure fair resource sharing across the platform.