Lesson 20 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 7 · Environment Management and Deployment

7.3 Sandbox selection, refresh, and data protection

4 min read Updated Nov 17, 2026

Exam objective

Select sandbox options for development and testing, and explain refresh and data-protection implications. Sandbox types differ in capacity, copied data, and intended use. A developer sandbox is suited to isolated development and metadata changes. A developer pro sandbox provides more storage for development data. Partial copy sandboxes include a selected subset of production data through a template, while full sandboxes can support high-fidelity testing with a larger production copy. Availability and limits depend on the Salesforce edition and current org entitlements. Select the smallest environment that supports the test rather than using a full copy by default.

A sandbox refresh replaces its contents from the production source according to the sandbox type and refresh process. It can overwrite development work, test records, users, and integration configuration. Plan refresh timing around release cycles, preserve source-controlled metadata, notify testers, and document any post-refresh setup steps. Confirm sandbox identity before making changes, especially when production and sandbox windows look similar. Sandbox banners, URLs, and clear naming conventions reduce the chance of production mistakes.

Data copied from production remains sensitive in a sandbox. Limit who can log in, remove unnecessary users, mask or synthesize personal values where supported, and review exports, email, and connected integrations. Disable or redirect outbound messages and jobs that could affect real customers. Credentials and endpoints should point to nonproduction systems. Test that the masking process does not break referential integrity or the business scenario being tested. Use separate environments for different purposes where team scale requires it: development, integration, user acceptance, and performance testing may have distinct needs. A full copy can help validate volume-sensitive behavior, while a smaller sandbox may be faster for an administrator to test a flow. Data refresh schedules and environment ownership should be documented. A sandbox with stale metadata may not reproduce a production issue; compare relevant settings before concluding that a fix is valid.

Before a refresh, identify unreleased work, test evidence, and data that must be retained. After refresh, validate user access, connected apps, certificates, named credentials, email deliverability, scheduled jobs, and integration endpoints. Reapply any approved configuration that is not copied or must differ by environment. Ensure automated tests do not send production messages. Track who performed the refresh and when, especially when audit or compliance procedures apply.

Exam focus: match sandbox type to development, partial-data, or full-volume test needs. Recognize that refresh overwrites sandbox content and that copied production data is not automatically de-identified. Keep metadata movement and data movement distinct. Include post-refresh validation and integration isolation in the plan. Extra concept: A sandbox is an operational environment with its own user and integration lifecycle, not just a disposable copy. Assign an owner who reviews access and configuration after each refresh.

A test plan should identify who can approve entry to the sandbox, who can extract its data, and when the copy will be destroyed or refreshed. Restrict access while masking is incomplete. If external teams need access, use named accounts and time-limited permissions. Confirm whether the environment contains realistic record ownership and sharing, because a data template that omits key users can make security tests invalid. After a refresh, test one access scenario and one integration scenario before inviting the broader test group. Add an explicit teardown step for temporary sandboxes and downloaded extracts. Confirm that access is removed when a vendor or project team finishes, and ensure backups or local exports follow the same retention policy as the sandbox. If realistic data is needed for a specific test, record why a synthetic dataset is insufficient and obtain the required approval before copying any sensitive records. Make the test owner responsible for confirming deletion and documenting any retained evidence.

Practical scenario

A team needs to test a migration against a representative subset of customer records and a separate team is developing a new flow. Use a partial-copy sandbox with a deliberate data template for acceptance testing and isolated developer sandboxes for flow work. Mask sensitive values, isolate endpoints, and document refresh dates. If the migration's performance depends on production-scale volume, schedule a full-copy or other approved scale test rather than assuming a small sample proves capacity.

Extra concept

Refresh cadence should align with release testing and data privacy controls. A frequent refresh can improve realism but increases the masking and reconfiguration workload; a stale sandbox can reduce privacy risk but may no longer represent production.

Key takeaways

  • Choose the smallest sandbox that supports the test objective.
  • A refresh overwrites sandbox work and may copy sensitive production data.
  • Mask data, isolate integrations, and verify access before testers return.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.data_sandbox.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.sandbox_refresh.htm&type=5
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator II simulator: same number of questions, same time limit.

Get Complete Access