HP0-J73 · Question #324
When designing a solution, what defines the length of time that is acceptable for a business to be without a specific application?
The correct answer is D. RTO. Recovery Time Objective (RTO) is the defined maximum duration a business can tolerate being without a specific application or service after an outage.
Question
When designing a solution, what defines the length of time that is acceptable for a business to be without a specific application?
Options
- ACall to repair
- BResponse time
- CSLO
- DRTO
How the community answered
(68 responses)- A1% (1)
- B6% (4)
- C3% (2)
- D90% (61)
Why each option
Recovery Time Objective (RTO) is the defined maximum duration a business can tolerate being without a specific application or service after an outage.
Call to repair refers to the act of contacting support to initiate a fix, not a defined tolerance threshold for application downtime.
Response time is a performance metric measuring system or network latency under normal operation, not an outage tolerance definition.
SLO (Service Level Objective) is a performance target within a broader SLA but does not specifically quantify the acceptable length of application unavailability.
RTO (Recovery Time Objective) is a disaster recovery metric that specifies the maximum acceptable downtime for a business application or process following a failure or disaster event. It is established during business impact analysis and directly drives recovery architecture decisions such as failover speed, replication frequency, and infrastructure investment.
Concept tested: Recovery Time Objective (RTO) definition in DR planning
Source: https://learn.microsoft.com/en-us/azure/reliability/disaster-recovery-overview
Topics
Community Discussion
No community discussion yet for this question.