A workload owner asks you to tighten ASR's crash-consistent recovery-point cadence from every 5 minutes to every 60 seconds to meet a tighter internal RPO target. The application can tolerate an RTO of 30 minutes. Which response matches the documented ASR design?
- ALower the crash-consistent recovery-point frequency to 60 seconds on the replication policy and reapply it to the protected items.
- BDecline the request; ASR creates crash-consistent recovery points every five minutes and the setting cannot be modified. Correct
- CSwitch the workload to Hyper-V replication, where Azure Site Recovery supports a 30-second crash-consistent interval for Azure VM A2A.
- DConfigure multi-VM consistency on the replication group; that overrides the five-minute crash-consistent default.
Why A is wrong: The crash-consistent five-minute interval is fixed; only app-consistent snapshot frequency and recovery-point retention are configurable on the replication policy.
Why B is correct: Correct. The ASR documentation states that crash-consistent recovery points are created every five minutes by default and that this setting cannot be modified.
Why C is wrong: The 30-second cadence applies to Hyper-V-to-Azure (H2A) replication, not to Azure VM A2A; mixing the two breaks the AZ-305 design.
Why D is wrong: Multi-VM consistency only synchronises recovery points across machines in the group; it does not change the underlying crash-consistent interval.