Imagine you're running a bakery.
RPO (Recovery Point Objective):
* How much bread can you afford to lose? This is your RPO. It's about the amount of data (or in this case, baked goods) you're willing to lose.
* Example: If your RPO is 2 hours, you can afford to lose up to 2 hours worth of baked goods in case of a disaster.
RTO (Recovery Time Objective):
* How long can you be out of business before it's too costly? This is your RTO. It's about the amount of time it takes to get back up and running.
* Example: If your RTO is 4 hours, you need to be able to reopen your bakery within 4 hours of a disaster.
Relating to the options:
* Options B and D directly relate to RTO because they focus on the time it takes to recover from a disaster (steps to recover and backup restoration time).
* Option A is about the importance of systems, not the time to recover.
* Option E is about the amount of data loss (RPO), not the time to recover (RTO).
In essence:
* RPO is about data loss.
* RTO is about time to recover.
Answer is CD:
When determining the Recovery Time Objective (RTO), several important factors should be considered:
Cost of Downtime:
Calculate the financial implications of service interruptions. This includes lost revenue, operational costs, and potential penalties for non-compliance with service level agreements (SLAs).
Data Backup Frequency:
Consider how often backups are performed. More frequent backups can reduce the amount of data loss and help in quicker recovery.
But it talks about A & E: "By understanding what is running and what the value is of all the running systems and applications, it becomes possible to calculate RTO. Keep in mind, however, there can be different RTO requirements based on application priority as determined by the value the application brings to the organization. Calculating RTO requires determining how quickly the recovery process for a given application, service, system or data needs to happen after a major incident based on the loss tolerance the organization has for that application, service, system or data as part of its BIA. Defining the loss tolerance involves how much operational time an organization can afford (or is willing) to lose after an incident before normal business operations must resume."
https://www.techtarget.com/whatis/definition/recovery-time-objective-RTO
But it talks about A & E:
"By understanding what is running and what the value is of all the running systems and applications, it becomes possible to calculate RTO. Keep in mind, however, there can be different RTO requirements based on application priority as determined by the value the application brings to the organization.
Calculating RTO requires determining how quickly the recovery process for a given application, service, system or data needs to happen after a major incident based on the loss tolerance the organization has for that application, service, system or data as part of its BIA. Defining the loss tolerance involves how much operational time an organization can afford (or is willing) to lose after an incident before normal business operations must resume."
upvoted 2 times
...
...
This section is not available anymore. Please use the main Exam Page.400-007 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Doobiedoo
Highly Voted 10 months agokalulosu
Most Recent 5 months agoRedrum702
8 months, 3 weeks agofamov66542
1 year, 1 month agofamov66542
1 year, 1 month agobdp123
1 year, 1 month agofamov66542
1 year, 1 month ago