On a newly provisioned instance nobody has ever created a custom update set. An administrator makes several configuration changes and then wants to move them to a test instance, but finds every change recorded against the Default update set. What is the Default update set, and what does this mean for moving the work?
- AIt is a temporary holding area that is cleared whenever the instance restarts, so the changes have already been discarded and the configuration work needs to be carried out again by hand.
- BIt is a system update set reserved for updates delivered by ServiceNow, so a customer update landing in it is a fault that has to be cleared before any transfer can be attempted.
- CIt is a permanent update set that collects customer updates whenever no other update set is current, and because it cannot be marked complete the changes must be moved into a new update set first. Correct
- DIt is an ordinary update set like any other, so marking it complete and retrieving it on the test instance moves the changes across with no further preparation needed.
Why A is wrong: Tempting because the name suggests a scratch area, but the Default update set is a persistent record and the customer updates in it are still present and recoverable.
Why B is wrong: Tempting because vendor supplied changes are handled differently from customer updates, but the Default update set exists precisely to catch customer updates made outside a named set.
Why C is correct: Correct: each application scope has a Default update set that acts as the catch all, it stays in progress permanently, and work sitting in it has to be moved into a transferable update set.
Why D is wrong: Tempting because it appears in the same list as other update sets, but it cannot be marked complete, so retrieval on the target instance is never offered for it.