Best practice ' Never assign a default update set as an update set' True/False ?

[sumanthkumar]

This is a recent question in my System Admin certification exam. Can anyone advise please ?

[amlanpal]

Hi Sumanth,

If my understanding is not wrong, it is said that not to use Default update set for capturing customization which are supposed to move different instances later. The best practice says to create and use new update sets and capture all your updates over there. So the answer should be 'True'.

I hope this helps.Please mark correct/helpful based on impact

[Harish KM]

The answer would be true. Because each time when you use a default update set for customisation. Once your development has done. you need to move that Update set to Test Instance. In this case you have to close the default Update set. And servicenow creates another default1 update set when you close the default update set. It is also not a good practice to use Default update set.

Best practice would be to use a update set with proper naming convention . Since many developers will be working on N number of update set. Just think in a real time scenario. There are 10 developers using the same default update set and your job is complete. You want to move your update set? How will you proceed? so thats the reason you have to use your own update sets.

[sreeram_nair]

You should not use the Default Update sets to move between instances. The default update set is a catch-all for admin only, not for migrating changes. Admins should use named update sets to move customizations between instances.