Exam SY0-501 topic 1 question 666 discussion

Non-persistent configuration means your configurations aren’t set in stone and can be rolled back easily enough to not cause any stress to the system.

Answer is 'A' (Non Persistence) as the exam objectives state the following: • Non-persistence - Snapshots - Revert to known state - Rollback to known configuration - Live boot media

When users access a nonpersistent desktop, none of their settings or data is saved once they log out. At the end of a session, the desktop reverts to its original state and the user receives a fresh image the next time he logs in.

When users access a nonpersistent desktop, none of their settings or data is saved once they log out. At the end of a session, the desktop reverts to its original state and the user receives a fresh image the next time he logs in.

Non-persistent configs usually refer to virtual environments. Once a non-persistent VDI reboots it pulls a fresh new template image. If, during testing, I realize that a new template image is no good (bad patch, corrupt driver, etc) I can just rollback and assign the previous image to the VDI, reboot, and it's all good again.

no wonder its number 666

Let start what is the rollback - revert to using the previous version of the system/software. What is the fault tolerance - it is refers to the ability of a system (computer, network, cloud cluster, etc.) to continue operating without interruption when one or more of its components fail For example, whe you have cluster or 2+ servers behind LB, they are fault tolerant and if one goes down, critical system platfoem is still run and up...So from my standpoint, that would be best rollback strategy

A. "Between uses and /or reboots, the operating environment and installed software are exactly the same". During the upgrade if one of the hardware/software is being upgrade fails, you can revert back to the original state. nonpersistent system is a computer system that does not allow, support, or retain changes. By: Comptia Security + Review Guide Fourth edition James Michael Stewart.

From MM's book: ... This might include reinstalling an operating system, or rebuilding from backups. These are time-consuming processes and ones to avoid by using less persistent systems. Achieving this means pursuing one of three options: • Virtualization/snapshots • Revert/rollback tools • Live boot ... I believe provided answer is correct.

Answer seems correct. We want the upgrade and any related config to be non-persistent in order to support rollback, if required. Fault tolerance is having RAID or an HA. Not sure how that would reduce risk if a rollback is needed.

my head hurts going back and forth to other sources. most said A, nother said D.

I'm leaning toward non-persistence configuration. Vmware has a page explaining its use, which is also discussed on page 263 here: https://books.google.com/books?id=qiDsEgYKXRAC&pg=PA263&lpg=PA263&dq=are+Non-persistent+configurations+used+for+critical+systems&source=bl&ots=_fHA33RKjw&sig=ACfU3U0XzghXT7ox-BCJCE3PeaT4ZEdhxA&hl=en&sa=X&ved=2ahUKEwjHzqqEqY_pAhVRa80KHfJiClIQ6AEwCXoECAgQAQ#v=onepage&q=are%20Non-persistent%20configurations%20used%20for%20critical%20systems&f=false

D VM Fault Tolerance provides continuous availability for virtual machines by creating and maintaining a Secondary VM that is identical to, and continuously available to replace, the Primary VM in the event of a failover situation. NOT A. A non-persistent configuration pertains to virtual desktops – it does not retain any data on the desktop itself after a logoff or reboot.