CSA Update Sets and Customizations 2 — Questions and Answers
Question 1: What happens to an update set when it is marked as 'Complete'?
- It is automatically pushed to the next instance
- It can no longer have new customizations recorded into it (Correct answer)
- It is deleted from the system after 30 days
- It is merged with the Default update set
Correct answer: It can no longer have new customizations recorded into it
Marking an update set as Complete closes it so no further changes are captured in it; you must create or switch to another update set.
Question 2: Which of the following update set states allows the set to be exported as an XML file?
- In Progress only
- Complete or In Progress (Correct answer)
- Complete only
- Ignore only
Correct answer: Complete or In Progress
Both In Progress and Complete update sets can be exported as XML files for transfer to another instance.
Question 3: When retrieving an update set from a remote instance, where does it first appear?
- In the Current Update Set picker
- In the Retrieved Update Sets list with a state of Loaded (Correct answer)
- In the Default update set automatically
- In the committed update sets log
Correct answer: In the Retrieved Update Sets list with a state of Loaded
Retrieved update sets appear in the Retrieved Update Sets list with a Loaded state and must be previewed and committed before they take effect.
Question 4: What is the purpose of running 'Preview' on a retrieved update set before committing?
- To compress the XML file size
- To detect potential conflicts with existing customizations (Correct answer)
- To automatically merge conflicting records
- To assign the update set to a specific application scope
Correct answer: To detect potential conflicts with existing customizations
Preview analyzes the update set for conflicts or problems before you commit it, allowing you to resolve issues proactively.
Question 5: Which record type is NOT typically captured in an update set?
- Business rules
- Script includes
- Data records such as incident tickets (Correct answer)
- UI policies
Correct answer: Data records such as incident tickets
Update sets capture configuration and customization changes, not data records like incidents, tasks, or user entries.
Question 6: An administrator needs to transfer a group of related customizations across instances in a specific order. What is the best approach?
- Export each update set individually and import in any order
- Use update set batching to define a sequential commit order (Correct answer)
- Manually re-create each customization on the target instance
- Combine all changes into the Default update set
Correct answer: Use update set batching to define a sequential commit order
Update set batching allows admins to group related update sets and define their commit sequence to handle dependencies correctly.
Question 7: What does the 'Ignore' state on an update set indicate?
- The update set has been committed successfully
- The update set will be skipped and not committed to the instance (Correct answer)
- The update set is pending review by another administrator
- The update set contains no customizations
Correct answer: The update set will be skipped and not committed to the instance
Setting an update set to Ignore marks it to be bypassed so it will not be committed, effectively discarding it without deleting the record.
What happens to an update set when it is marked as 'Complete'?