ServiceNow CPOA free question 5 / 10 · Domain 3: Process
A developer asks why the team should use Developer Sandboxes instead of each developer working in a personal developer instance (PDI). What does the overview note say PDIs lack?
- A controlled baseline configuration to start from
- The ability to use ServiceNow Studio or ServiceNow IDE
- Access to the ServiceNow Store for installing applications
- Support for Git source control, so work is not versioned
Show the answer and explanation
Answer: A
Why this is correct
The overview on Exploring Developer Sandboxes says the feature aims to provide lower-cost developer isolation and parallelism, and lists its benefits: isolation, faster delivery, safe testing, and on-demand provisioning. A note then says Personal Development Instances (PDIs) are still available, but they don't have a controlled baseline configuration like Developer Sandboxes do. Each sandbox contains the full metadata of the base instance, so every developer starts from the same configuration, which is what makes merging their work predictable. A PDI starts from its own state instead.
Why the other options are wrong
"Access to the ServiceNow Store for installing applications" … Store access is not mentioned in the PDI note. The note compares PDIs and sandboxes on one point, the baseline configuration.
"The ability to use ServiceNow Studio or ServiceNow IDE" … The note does not say PDIs cannot run development tools. It says PDIs are still available but do not have a controlled baseline configuration.
"Support for Git source control, so work is not versioned" … Source control is not the difference the note draws. Its point is that sandboxes start from a controlled baseline and PDIs do not.
Other notes on the page
The page also notes that cloning and upgrading an instance removes all sandboxes from the instance, and that Build Agent is supported in Developer Sandboxes.
Go to the ServiceNow CPOA practice app (10 free questions; purchase unlocks all questions)