Praxis Academy
Home › Platform App Builder › App Deployment

Platform App Builder practice questions: App Deployment

App Deployment is 13% of the Salesforce Certified Platform App Builder exam. It covers sandboxes, change sets, packages and DevOps Center. Try these 9 free questions, then open each answer to see why every option is right or wrong.

01

An app builder at an outdoor retailer has built a sandbox template covering Accounts, Projects and Project Milestones in order to rework some flows in the project management app. What kind of testing environment should be created?

  1. Developer Pro
  2. Partial Copy
  3. Scratch Org
  4. Developer
Show answer

Answer: B

A. Developer ProIncorrect. A Developer Pro sandbox copies metadata only and does not use sandbox templates.
B. Partial Copy ✓Correct. Partial Copy sandboxes apply a sandbox template to copy sample data from the selected objects.
C. Scratch OrgIncorrect. Scratch orgs are short-lived, source-driven environments without sandbox templates.
D. DeveloperIncorrect. A Developer sandbox copies metadata only and does not use sandbox templates.

Why: Sandbox templates choose which objects have a sample of production data copied into the sandbox. Among the options, only a Partial Copy sandbox uses templates, so it is the environment that brings in data for Accounts, Projects and Project Milestones and lets the flows be tested against realistic records without copying the entire database. Reference: Create or Edit Sandbox Templates

02

A Platform App Builder deployed a change set from a sandbox to production, and the deployment is taking a very long time. What explains the delay?

  1. The change set contains dependent fields.
  2. The change set contains profiles.
  3. The change set contains a change to a field's type.
  4. The change set contains roles.
Show answer

Answer: C

A. The change set contains dependent fields.Incorrect. Dependent field definitions are lightweight metadata and do not slow deployment.
B. The change set contains profiles.Incorrect. Profiles hold permission settings and do not trigger data conversion.
C. The change set contains a change to a field's type. ✓Correct. A data type change requires converting existing values on every record, which can make deployment slow.
D. The change set contains roles.Incorrect. Roles are lightweight metadata and do not slow deployment.

Why: Changing a field's data type forces Salesforce to convert every value already stored in that field across all records. The more records with data in the field, the longer the conversion and therefore the deployment. Most other metadata, such as profiles, roles or dependent field definitions, does not require any data conversion. Reference: Change Sets Best Practices

03

A Platform App Builder must set up a sandbox for a developer who will test with substantial sample data sets requiring up to 250 MB of storage. The sandbox will be refreshed daily. Which sandbox type fits?

  1. Full
  2. Developer
  3. Partial Copy
  4. Developer Pro
Show answer

Answer: D

A. FullIncorrect. A Full sandbox can be refreshed only every 29 days.
B. DeveloperIncorrect. A Developer sandbox tops out at 200 MB of data.
C. Partial CopyIncorrect. A Partial Copy sandbox can be refreshed only every 5 days.
D. Developer Pro ✓Correct. Developer Pro provides 1 GB of data storage and supports daily refreshes.

Why: A Developer Pro sandbox offers 1 GB of data storage, enough for 250 MB, whereas a Developer sandbox is limited to 200 MB. Developer Pro can also be refreshed once a day. Partial Copy (every 5 days) and Full (every 29 days) cannot meet the daily refresh requirement. Reference: Sandbox Types and Templates

04

A Platform App Builder at an outdoor gear retailer has finished a new commission calculation flow, plus its supporting components, in a Developer sandbox. The project lead insists that sales operations users confirm the calculation using real Opportunity data before anything goes to production. A Full sandbox is available. What deployment approach should the app builder follow?

  1. Use a change set with the Validate Only option to send the components from the Developer sandbox to production, then run User Acceptance Testing (UAT) in production.
  2. Refresh the Developer sandbox from production so it receives real Opportunity data, run User Acceptance Testing (UAT) there, then deploy to production.
  3. Move the components from the Developer sandbox straight to production and let sales operations users verify them in production.
  4. Move the components from the Developer sandbox into the Full sandbox, run User Acceptance Testing (UAT) in the Full sandbox, then deploy to production.
Show answer

Answer: D

A. Use a change set with the Validate Only option to send the components from the Developer sandbox to production, then run User Acceptance Testing (UAT) in production.Incorrect. Validate Only performs no deployment, and running UAT in production puts live data at risk.
B. Refresh the Developer sandbox from production so it receives real Opportunity data, run User Acceptance Testing (UAT) there, then deploy to production.Incorrect. Refreshing a Developer sandbox brings over metadata only, so no real Opportunity data arrives.
C. Move the components from the Developer sandbox straight to production and let sales operations users verify them in production.Incorrect. Going directly to production skips UAT and exposes business data to risk.
D. Move the components from the Developer sandbox into the Full sandbox, run User Acceptance Testing (UAT) in the Full sandbox, then deploy to production. ✓Correct. The Full sandbox carries a copy of production data, so sales operations can test with real records before the production deployment.

Why: The flow was built in a Developer sandbox, which holds no real Opportunity records, yet sales operations must test it against real data before go-live. A Full sandbox is a complete replica of production, data included. Promoting the components there lets testers run UAT on realistic Opportunities without touching live records. Once UAT passes, the change moves on to production. Testing with realistic data before a production release is the documented best practice. Reference: Change Sets

05

A Platform App Builder at a pharmaceutical company has built an HR Onboarding application made up of custom objects, page layouts, Lightning record pages, and an Apex class. The work lives in a Developer sandbox of the company's production org. A wholly owned subsidiary runs its own separate Salesforce production org, which has no deployment connection to the parent's production org. The app builder needs to transfer the HR Onboarding application from the parent's Developer sandbox into the subsidiary's production org so it can be evaluated. What deployment approach should the app builder take?

  1. Refresh one of the subsidiary's sandboxes from the parent's Developer sandbox, then deploy from that sandbox with change sets.
  2. Build an unmanaged package in the parent's Developer sandbox and install it in the subsidiary's production org through the install URL.
  3. Upload an outbound change set from the parent's Developer sandbox to the subsidiary's production org.
  4. Build a managed package in the parent's Developer sandbox and install it in the subsidiary's production org through the install URL.
Show answer

Answer: B

A. Refresh one of the subsidiary's sandboxes from the parent's Developer sandbox, then deploy from that sandbox with change sets.Incorrect. A sandbox belonging to another org cannot be refreshed from your own org.
B. Build an unmanaged package in the parent's Developer sandbox and install it in the subsidiary's production org through the install URL. ✓Correct. An unmanaged package installs via URL with no deployment connection, and the receiving org can edit every component.
C. Upload an outbound change set from the parent's Developer sandbox to the subsidiary's production org.Incorrect. Change sets depend on a deployment connection between related orgs, and none exists here.
D. Build a managed package in the parent's Developer sandbox and install it in the subsidiary's production org through the install URL.Incorrect. Managed packages are meant for distributing and upgrading IP-protected apps, which a one-time transfer doesn't need.

Why: The application must reach a separate, unconnected production org, and only for evaluation rather than ongoing distribution. Change sets need a deployment connection between related orgs, which is missing here. Packages, by contrast, move metadata between unrelated orgs through an install URL. An unmanaged package suits a one-time transfer for evaluation: the installing org fully owns and can edit the components, and no upgrade path or IP protection is required. Reference: Ways to Distribute Your Application

06

A renewable energy firm wants to test code against a subset of production data smaller than 5 GB, and it wants to refresh that sandbox every weekend. Which sandbox type fits these needs?

  1. Developer Pro
  2. Partial Copy
  3. Full Copy
  4. Developer
Show answer

Answer: B

A. Developer ProIncorrect. Developer Pro sandboxes contain no production data.
B. Partial Copy ✓Correct. It holds up to 5 GB of production data and can be refreshed every 5 days.
C. Full CopyIncorrect. A Full Copy sandbox copies all data and allows a refresh only every 29 days.
D. DeveloperIncorrect. Developer sandboxes contain no production data.

Why: Two requirements must be met: real production data up to 5 GB, and a weekly refresh. A Partial Copy sandbox holds a template-defined subset of production data with a 5 GB storage limit, which covers the data need. Its minimum refresh interval is 5 days, shorter than a week, so weekend refreshes are allowed. Reference: Sandbox Types and Templates | Salesforce Help

07

A Platform App Builder at a biotech firm is about to deploy a release from a Full sandbox to production. The deployment triggers the complete Apex test suite, which runs for roughly 30 minutes. The team has booked a Saturday morning cutover window and wants the deployment to take up as little of that window as possible. What deployment approach should the app builder use?

  1. Upload the outbound change set when the cutover window opens and click Deploy.
  2. Upload the outbound change set during the cutover window and choose Run Local Tests to shorten the deployment.
  3. Upload the outbound change set, run Validate Only against production the day before the cutover, then click Quick Deploy when the cutover window opens.
  4. Upload the outbound change set the day before the cutover, then click Deploy when the cutover window opens.
Show answer

Answer: C

A. Upload the outbound change set when the cutover window opens and click Deploy.Incorrect. Deploying inside the window runs the full 30-minute test suite during the cutover.
B. Upload the outbound change set during the cutover window and choose Run Local Tests to shorten the deployment.Incorrect. Running only local tests may not satisfy the requirement and still executes tests in the window.
C. Upload the outbound change set, run Validate Only against production the day before the cutover, then click Quick Deploy when the cutover window opens. ✓Correct. Tests run during validation a day early, and Quick Deploy (valid for 10 days) deploys in the window without re-running them.
D. Upload the outbound change set the day before the cutover, then click Deploy when the cutover window opens.Incorrect. An early upload doesn't stop tests from running when Deploy is clicked.

Why: The team wants to keep the 30-minute Apex test run out of the limited Saturday window. Validate Only compiles the code and runs the full test suite against production without deploying, so any failures surface early enough to fix. A successful validation stays valid for up to 10 days, and Quick Deploy then deploys without re-running tests, making the in-window step fast. Reference: Validate a Deployment (Quick Deploy)

08

An app builder needs a sandbox where users can run user acceptance testing on the newest developer features. It should contain roughly 500MB of data defined through a template and be refreshed every week. Which sandbox satisfies these requirements?

  1. Full sandbox
  2. Developer Pro sandbox
  3. Developer sandbox
  4. Partial Copy sandbox
Show answer

Answer: D

A. Full sandboxIncorrect. A Full sandbox copies all data and allows a refresh only every 29 days.
B. Developer Pro sandboxIncorrect. Developer Pro sandboxes provide no template-based data.
C. Developer sandboxIncorrect. Developer sandboxes provide no template-based data and only 200 MB of storage.
D. Partial Copy sandbox ✓Correct. It copies up to 5 GB of data through a template and can be refreshed every 5 days.

Why: Three clues narrow the choice: data loaded through a template, about 500MB of it, and a weekly refresh. A Partial Copy sandbox uses a sandbox template to copy a sample of production data from selected objects and supports up to 5GB, easily covering 500MB. It can be refreshed every 5 days, so weekly refreshes work. With realistic production data rather than metadata only, it is the recommended environment for QA and UAT. A Full sandbox copies everything and refreshes far less often, and Developer sandboxes offer no template-based data. Reference: Sandbox Types and Templates | Salesforce Help

09

Some custom objects in a production org store confidential information. The team needs a sandbox that contains data records, leaves out every confidential object, and can be refreshed each week. What should an app builder do to satisfy these requirements?

  1. Create a Developer Pro Sandbox and schedule Data Loader to download data from selected objects every week.
  2. Create a Full Copy Sandbox and apply a sandbox template.
  3. Create a Partial Copy Sandbox and apply a sandbox template.
  4. Create a Developer Sandbox and schedule Data Loader to download data from selected objects every week.
Show answer

Answer: C

A. Create a Developer Pro Sandbox and schedule Data Loader to download data from selected objects every week.Incorrect. Developer Pro sandboxes contain no production data and don't support templates, and scripting Data Loader is a manual workaround.
B. Create a Full Copy Sandbox and apply a sandbox template.Incorrect. Full sandboxes do support templates, but they can be refreshed only every 29 days, not weekly.
C. Create a Partial Copy Sandbox and apply a sandbox template. ✓Correct. With a template it copies data only from the chosen objects, and it can be refreshed every 5 days.
D. Create a Developer Sandbox and schedule Data Loader to download data from selected objects every week.Incorrect. Developer sandboxes contain no production data and don't support templates.

Why: The sandbox must hold real records, exclude the confidential objects, and support weekly refreshes. A Partial Copy sandbox gets its data subset from a sandbox template, in which the app builder picks which objects to include and can leave the confidential ones out. It can be refreshed every 5 days, which covers a weekly cadence. A Full Copy sandbox refreshes only every 29 days, and Developer or Developer Pro sandboxes carry no production data and don't use templates. Reference: Sandbox Types and Templates | Salesforce Help

Find out if you're ready to pass

Take the free Platform App Builder diagnostic: 20 questions, no account needed. Then unlock all 241 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam