Development & Deployment 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 Development & Deployment flashcards as text
A team needs to run different Apex tests for different deployment scenarios (smoke tests vs. full regression). Which feature supports organizing tests into named groups?
Answer: Apex Test Suites
Apex Test Suites allow grouping of test classes into named collections that can be run together, supporting different testing scenarios.
An architect discovers that a Queueable Apex job is enqueuing additional Queueable jobs in a chain, causing delays. What is the platform limit for Queueable job chaining?
Answer: Maximum 50 jobs in the Apex flex queue, but no limit on chaining depth
While the Apex flex queue holds up to 50 Queueable jobs, there is no strict limit on chaining depth, but the flex queue capacity constrains how many can be queued at once.
A company wants to validate their deployment package against production before executing it, without making any changes. Which deployment option supports this?
Answer: Both B and C are correct
Both the Metadata API checkOnly=true flag and the Change Set 'Validate Only' option perform a test deployment that checks for errors without actually changing the org.
Which Apex governor limit applies per-transaction and is MOST commonly violated when processing large datasets in triggers?
Answer: Maximum CPU time: 10,000ms for synchronous transactions
CPU time (10,000ms for synchronous, 60,000ms for asynchronous) is the governor limit most commonly hit during complex bulk processing in triggers.
An architect wants to ensure that custom metadata changes made by one team do not break another team's work in their respective scratch orgs. What strategy BEST prevents this?
Answer: Implement feature branch workflows in version control with scratch orgs per feature
Feature branch workflows with per-feature scratch orgs isolate each team's changes, preventing conflicts until branches are merged through a pull request process.
A deployment to production fails because a required Apex class referenced in a Flow is not included in the change set. What is the ROOT CAUSE?
Answer: The change set package.xml did not include the dependent Apex class
Change sets and deployment packages must include all dependent components; omitting a referenced Apex class causes validation failure due to unresolved dependencies.
An architect needs to enforce that every Apex class deployed to production has at least one corresponding test class. Which approach enforces this at scale?
Answer: A CI/CD pipeline step that parses test coverage reports and blocks merges below threshold
A CI/CD pipeline gate that parses coverage reports and blocks merges below the required threshold enforces test class coverage automatically at scale.