An IaaS application has a two-hour RTO and four-hour RPO. The application takes one hour to back up its data or restore from a local backup file. A systems administrator is tasked with configuring the backup policy. Which of the following should the administrator configure to achieve the application requirements with the LEAST cost?
To meet the application's requirements of a two-hour RTO and four-hour RPO, the backup strategy should ensure data is backed up frequently enough to avoid data loss and be restored within the required time frame. Specifically, backing up to long-term storage every four hours ensures that the maximum data loss does not exceed four hours, meeting the RPO requirement. Additionally, utilizing long-term storage is likely to be more cost-effective compared to object storage. The backup duration of one hour will fit within the RTO timeline, allowing for data restoration within two hours if necessary.
The correct answer is B. Source: IT Pro Academy Long-term storage is used to store the data accessed rarely or mostly saved for archive purposes. It should not be used to store backup data than must be restored in two hour since data in the long-term storage can take several hours to retrieve depending on the specified rehydration priority. Back up to object storage every hour or three hours both accommodate the requirement of RTO and RPO. However, the option of backup every three hours is less expensive.
Based on the application's RTO and RPO, the administrator needs to make sure that data can be restored within four hours, and the application can be brought back online within two hours. As the backup takes one hour, this leaves only one hour for the restoration process. Option A, backing up to long-term storage every night, would have an RPO of 24 hours, which does not meet the application's requirements. Option B, backing up to object storage every three hours, would have an RPO of three hours and would provide more frequent backups than necessary, increasing costs. Option D, backing up to object storage every hour, would provide more frequent backups than necessary, increasing costs, and would not meet the RPO of four hours since data restoration takes one hour, and backups occur every hour. Therefore, the best option would be to back up to long-term storage every four hours, with an RPO of four hours, which meets the application's requirements with the least cost. So, the correct answer is option C.
Given: RTO (Recovery Time Objective): 2 hours RPO (Recovery Point Objective): 4 hours Backup duration: 1 hour We need to choose an option that allows us to restore the application within 2 hours (RTO) and ensures that the data loss does not exceed 4 hours (RPO). Option D. Back up to object storage every hour. This option aligns with the RPO of 4 hours, as backups are taken every hour. It also aligns with the RTO of 2 hours, as the backups can be restored from object storage within 2 hours. Since the application takes one hour to back up its data or restore from a local backup file, this option ensures that backups are taken frequently enough to meet the RPO and RTO requirements effectively. Therefore, the correct option is D. Back up to object storage every hour.
Answer is likely B
Just as "SimplyDebonair" states.
This question should be a little more clear with what it wants. C is the cheapest option that fits the requirements that are stated in the question, but generally speaking you wouldn't put backup data into a long term storage. It is possible to retrieve your data within the time frame you want, but not always. B is the "more correct" answer but it is also more expensive. Annoying
C. Back up to long-term storage every four hours: This option aligns with the RPO of four hours, ensuring that data is backed up at least every four hours. It also balances the cost by using long-term storage, which is typically cheaper compared to more frequent backups to object storage. B. Back up to object storage every three hours: This option meets the RPO of four hours and provides more frequent backups, but it may not be necessary based on the application's RPO and RTO requirements, potentially increasing cost unnecessarily.