Designing Microsoft Azure Infrastructure Solutions (AZ-305) — All Questions
4 questions
A mission-critical application must resume in a second Azure region within an hour if the primary region fails, with orchestrated failover of multi-tier VMs. Which service should the architect design in?
- a.Azure Backup only
- b.Azure Site Recovery✓
- c.A single Availability Zone deployment
- d.Azure Policy
Azure Site Recovery replicates VMs to a secondary region and orchestrates failover and failback with recovery plans, meeting a low RTO for regional outages. Backup restores data but is not fast orchestrated regional failover, a single zone does not survive a regional failure, and Policy governs configuration.
A design requires that backups cannot be deleted or altered by an attacker who compromises an admin account. Which backup design feature addresses this?
- a.Storing backups on the source VM
- b.Reducing retention to one day
- c.Disabling soft delete
- d.Immutable/soft-delete-protected Recovery Services vault✓
Immutability and soft delete on the Recovery Services vault prevent backups from being permanently deleted or tampered with, defending against malicious or accidental deletion. Keeping backups on the source VM, shortening retention, or disabling soft delete all weaken protection.
A business states that after a failure it can lose at most five minutes of data. Which objective does this define, and what does it drive?
- a.RPO, which drives backup/replication frequency✓
- b.RTO, which drives datacenter location
- c.SLA, which drives support plan
- d.Latency, which drives region choice
The maximum acceptable data loss is the recovery point objective (RPO); a five-minute RPO drives how frequently data must be backed up or replicated. RTO concerns downtime, an SLA is a service commitment, and latency is a performance measure.
To maximize availability of a stateless web tier within a single region against a datacenter failure, which design should the architect use?
- a.Deploy all instances to one datacenter
- b.Use a single large VM
- c.Distribute instances across Availability Zones behind a zone-redundant load balancer✓
- d.Rely on nightly backups only
Spreading instances across Availability Zones behind a zone-redundant load balancer keeps the tier available if one datacenter (zone) fails. A single datacenter or single VM is a single point of failure, and nightly backups aid recovery but do not provide high availability.