What type of sandbox should each team member use?

DreamHouse Realty is rethinking its sandbox utilization strategy after acquiring Cloud Kicks. The Salesforce COE already utilizes a partial and a full sandbox, which it refreshes on their own regular schedules. Teams are expanding and have to begin each of their small projects in a sandbox before committing to the larger pool for collaborative testing while still keeping costs down.

What type of sandbox should each team member use?
A . Full sandbox
B . Developer sandbox
C . Developer pro sandbox
D . Partial sandbox

Answer: B

Explanation:

The best type of sandbox for each team member to use is a developer sandbox. A developer sandbox is a copy of production that includes only the metadata, such as objects, fields, layouts, etc. It does not include any data, such as records or attachments. A developer sandbox is ideal for small projects that do not require data testing, such as developing new features or customizations. A developer sandbox has a storage limit of 200 MB and can be refreshed once per day. A developer sandbox is also cheaper than other types of sandboxes. A full sandbox is a copy of production that includes all the metadata and data. It is ideal for large projects that require data testing, such as performance testing or integration testing. A full sandbox has the same storage limit as production and can be refreshed every 29 days. A full sandbox is also the most expensive type of sandbox. A developer pro sandbox is similar to a developer sandbox, but it has a larger storage limit of 1 GB and can be refreshed every 5 days. It is ideal for projects that require some data testing, such as data migration or quality assurance testing. A partial sandbox is similar to a full sandbox, but it has a smaller storage limit of 5 GB and can be refreshed every 5 days. It is ideal for projects that require selective data testing, such as user acceptance testing or staging testing