Rollbacks – Application Management – SOA-C02 Study Guide

Rollbacks

A rollback is a method of undoing the steps taken during a patch. In some cases, a patch may not permit a rollback. In these situations, you want to make sure you test the patch in a testing environment and make sure you back up all related data before patching a live system. You should also have another plan in place to recover the software, which could include performing a full backup on all software before implementing the patch.

ExamAlert

The exam objectives that are related to this section are

Select deployment scenarios and services (for example, blue/green, rolling, canary)

Implement automated patch management

Note that these objectives do not list any specific AWS services. However, many of these tools, including OpsWorks, Systems Manager, and CloudFormation, are covered in this chapter and in Chapter 7.

Cram Quiz

Answer these questions. The answers follow the last question. If you cannot answer these questions correctly, consider reading this section again until you can.

1. You have determined that there is a problem with a patch that was recently deployed. Which method would be the best solution to undo the actions that were taken when the patch was deployed?

A. Restore the backup.

B. Perform a rollback.

C. Reinstall software.

D. Delete the patch.

2. Which of the following patch types is most likely to be the responsibility of AWS?

A. VMs

B. Virtual appliances

C. Custom applications

D. Firmware

Cram Quiz Answers

1. Answer: B is correct. A rollback is the best method of undoing the steps taken during a patch. In some cases, a patch may not permit a rollback. In these situations, you want to make sure you test the patch in a testing environment and make sure you back up all related data before patching a live system. You should also have another plan in place to recover the software, which could include performing a full backup on all software before implementing the patch.

2. Answer: D is correct. Firmware is software that is designed to provide control over device hardware. In a public cloud, customers rarely have any control over the firmware that is being utilized by the physical hardware (exceptions can include when a customer leases the entire physical system for their use). As a result, the patching of firmware in a public cloud is almost always fully in the scope of the cloud vendor.

What Next?

If you want more practice on this chapter’s exam objectives before you move on, remember that you can access all of the Cram Quiz questions on the Pearson Test Prep software online. You can also create a custom exam by objective with the Online Practice Test. Note any objective you struggle with and go to that objective’s material in this chapter.