You are modifying an existing disaster recovery solution for an Azure SQL managed instance that contains a failover group named FG1. You need to ensure the maximum in-transit time for FG1 when an…

Question

Options

• Aan availability group
• Ba secondary managed instance
• Ca failover policy
• Da grace period

• A
  6% (2)
• B
  9% (3)
• C
  3% (1)
• D
  81% (26)

Explanation

Explanation

Grace Period is the correct configuration because it defines the amount of time (in hours) that Azure will wait before triggering an automatic failover after a failure is detected - directly controlling the maximum in-transit (data loss) time during an automatic failover event for a failover group like FG1.

Why the distractors are wrong:

• A (Availability Group): Availability groups are a SQL Server on-premises/IaaS concept; Azure SQL Managed Instance uses failover groups, and configuring an availability group wouldn't address automatic failover timing.
• B (Secondary managed instance): A secondary managed instance is a prerequisite for the failover group to exist - it enables replication but doesn't control the timing of automatic failover.
• C (Failover policy): The failover policy determines whether automatic failover occurs (Automatic vs. Manual), not how long the system waits before triggering it.

Memory Tip: Think of the Grace Period as a "countdown timer" - it's the window you set to control when the system pulls the failover trigger, giving you influence over maximum acceptable downtime and data loss during automation. "Grace = time you're given before failover fires."

No community discussion yet for this question.