CSA - Data Migration and Integration (13% of the exam) - Section 6
System update sets
Capturing configuration changes in update sets, the current update set, what is and is not tracked (data records are not), merging and batching, exporting and retrieving between instances, previewing and committing, resolving collisions, and the role of the Default update set.
Update sets
Practice question for this objective
lock_openFree sampleData Migration and Integrationhard
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.check_circle 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.
The Default update set is a permanent collection point for changes made when no other update set is current, and it cannot itself be transferred. The platform needs somewhere to record a customer update when the session has no user selected update set, so every application scope carries a Default update set that stays in progress for the life of the instance. Because a set can only be retrieved once its state is Complete, and the Default set can never reach that state, the captured updates must be moved into a new update set before any transfer.
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.
Answers that look right on this material and are not. Each one is a distractor from a different question in the CSA bank for this domain.
Both the field and the business rule are captured in Default, and the 200 rows are captured with them because they live in the same table.
errorWhy it is wrong: Tempting because everything happened in one table in one session, but an update set records configuration changes only, so the inserted rows are never written as customer updates regardless of the table.
The selection applies to the whole instance, so both administrators record their changes into HR Release 2 until one of them selects another set.
errorWhy it is wrong: Tempting because the picker sits in the instance header, but the choice is personal to the signed in user and does not redirect a colleague's work.
The new table definition, because table records created through the schema tools are stored as data and have to be built again by hand on the target instance.
errorWhy it is wrong: Tempting because a table feels like data rather than configuration, but a table and its column definitions are dictionary records captured as customer updates and they do travel in the update set.