Domain 6 — Dev Lifecycle Flashcards

AI-Generated Content

These flashcards were generated with AI assistance and may need human review for accuracy. Always verify against official Salesforce documentation.

Scenario-based cards testing architectural judgment on environment strategy, CI/CD pipelines, governance, testing, and risk management.

Keyboard shortcuts: Space or Enter to flip · Arrow keys to navigate · 1–3 to grade after flipping

Card 1 of 9

A company has 3 development teams working on independent feature streams with monthly production releases. They currently share one Developer sandbox and a single staging sandbox, causing frequent deployment conflicts. Redesign their environment strategy.

Per-team sandboxes + shared integration: (1) Developer Pro sandboxes: one per developer (or pair) for isolated feature development. Scratch orgs for short-lived spikes and CI jobs. (2) Integration sandbox (Partial Copy): shared environment where all teams merge and test together before staging — this is where cross-team conflicts surface early. (3) Staging/UAT sandbox (Full Copy): mirrors production data for realistic testing, used for final UAT before release. (4) Hotfix sandbox (Developer): dedicated to production bug fixes, bypasses the feature pipeline. Branching strategy: feature branches per team, merge to develop (deploys to Integration), merge to release (deploys to Staging), merge to main (deploys to Production). Refresh cadence: Dev Pro sandboxes refresh after each release, Full Copy quarterly, Partial Copy monthly. Trade-off: more sandboxes = more licensing cost and refresh management. But the cost of deployment conflicts (delayed releases, regression bugs) far exceeds the sandbox cost.

Click card or press Space to reveal answer

← PrevNext →

How Spaced Repetition Works

Rate each card 1–3 after flipping. Rating 1 (Again) resets the interval. Rating 2 (Good) advances normally. Rating 3 (Easy) extends the interval. Check your progress dashboard to see what’s due.