AAA Financial Services Company is performing implementation planning for a core switch upgrade. The company has 200 financial software programmers that work billable hours during the week. They have critical, scheduled money transfer transmissions that occur at hourly intervals every night. There are two, two-hour long IT maintenance windows scheduled for software upgrades, one on Saturday and one on Sunday. The bank advertises online banking as available 24 hours on business days and 21 hours on the weekends. However, a network upgrade that is necessary to replace some switches is expected to take four hours. Because of rack constraints, this time includes three hours to remove the old switches before the new switches can be installed and one hour to test the logical configuration. How should the implementation scheduling be handled

IT Questions Bank › Category: CCNA Discovery v4 › AAA Financial Services Company is performing implementation planning for a core switch upgrade. The company has 200 financial software programmers that work billable hours during the week. They have critical, scheduled money transfer transmissions that occur at hourly intervals every night. There are two, two-hour long IT maintenance windows scheduled for software upgrades, one on Saturday and one on Sunday. The bank advertises online banking as available 24 hours on business days and 21 hours on the weekends. However, a network upgrade that is necessary to replace some switches is expected to take four hours. Because of rack constraints, this time includes three hours to remove the old switches before the new switches can be installed and one hour to test the logical configuration. How should the implementation scheduling be handled

Defer the software upgrades. Use the Saturday window to perform the hardware installation. Use the Sunday window to perform the logical testing.
Coordinate and publish a separate four-hour downtime during Friday to perform the complete switch installation and testing process. Use the Saturday and Sunday windows to correct any outage problems after the Friday window.
Coordinate and publish two, four-hour downtimes incorporating the published Saturday and Sunday windows. Defer any software upgrades until the new network is proven to be working correctly with the old software. Use the Sunday window as a fallback scheduling period if there are problems necessitating backing out of the Saturday window.
Coordinate and publish an eight-hour downtime incorporating the Saturday window. This will allow four hours for installation and logical testing, one hour for troubleshooting and decision, and three hours to roll back to the previous configuration if the new switching cannot pass the logical testing. Defer any software upgrades until the new network is proven to be working correctly with the old software.

Exam with this question: CCNA Discovery 4: DCompNtwk Chapter 9 Exam