


Pretty sure you want to start with review release notes, then schedule the maintenance window, check the system health, and finally backup config. That way you know what might go wrong before you even touch the system. Order: review release notes → schedule maintenance → check system health → backup config. I think that's what Dell recommends but let me know if you see it differently.
I don't think you should put backup config before reading release notes. Most Dell docs and similar exam questions have the order as: review release notes, schedule maintenance window, check system health, then finally backup config. Backup is important but you need to know what changes are coming first. The trap is putting backup too early, so watch out for that. Agree?
- Review release notes → Schedule maintenance → Check system health → Backup config
I usually see the order as: review release notes first, then schedule maintenance window, check system health, and finally backup config. That aligns with Dell's docs I think. The idea is you verify info and downtime before touching systems or configs. Unless anyone found a different sequence on the exam?

Pretty sure the order is: A A to B B, A B to A A, B A to A B, B B to B A. Looks like Dell tries to trip people up by switching the port letters around. Similar pattern showed up in practice questions.

Man, Dell loves to overcomplicate these steps. Looks like this:
- Upload → receives the package
- Health check → run in parallel on all appliances
- Upgrade → starts with the master appliance
- Commit → delete and mark the new version as current
Pretty sure that lines up with what I remember from similar practice questions, but could be missing some nuance for legacy models.