CCNA Ha Dr Environment Questions

Option C is correct because active geo-replication allows you to create a readable secondary in another region with an RPO of 5 seconds and manual failover, which can meet the RTO if automated via scripts. Failover groups have a default RPO of 5 seconds but an RTO of 1 hour; however, active geo-replication with a manual failover script can achieve the required RTO. Zone redundancy does not protect against regional outage.

Backup restore has higher RPO.

Options A, B, and D are correct. A failover group requires a primary server, a secondary server, and at least one database. Option C is wrong because a listener is automatically created, not required to be configured.

Option E is wrong because an elastic pool is optional.

Option A is correct. The readOnlyEndpoint failoverPolicy is Disabled, meaning the read-only listener will not automatically redirect connections after failover. Option B (automatic failover with data loss) is correct but not the best answer; the read-only endpoint behavior is the key point.

Option C (read-write endpoint) is automatic. Option D (read-only endpoint) is disabled, so it does not affect read-write connections.

Option C is correct because the sys.dm_geo_replication_link_status DMV shows replication lag and the last replicated transaction. Option A is wrong because sys.dm_database_copies is for copy-only operations. Option B is wrong because sys.dm_continuous_copy_status is deprecated.

Option D is wrong because sys.dm_replication_status is for transactional replication.

Option A is correct because Business Critical tier with failover groups offers an RTO of ~30 seconds and RPO of 0 (zero data loss) when using synchronous replication. Option B is wrong because RTO is lower. Option C is wrong because RPO is zero.

Option D is wrong because RPO is zero.

Option A is correct because Hyperscale supports geo-replication to a secondary region. Option B is wrong because zone redundancy is within region. Option C is wrong because failover groups are supported but require geo-replication.

Option D is wrong because geo-restore has higher RPO.

Option B is correct because Business Critical tier with zone-redundancy provides 99.995% SLA within a region, but to withstand a regional outage you need a failover group with active geo-replication. Option A is wrong because General Purpose with geo-replication has lower SLA. Option C is wrong because Business Critical without geo-replication cannot withstand a regional outage.

Option D is wrong because Hyperscale with geo-replication has different SLA.

Option B is correct. Setting highAvailabilityReplicaCount to 2 in Business Critical tier creates two additional readable replicas (total of 3 replicas including primary). This improves read performance by allowing more read-only connections to be offloaded to replicas.

Option A (zero data loss) is achieved by synchronous replication, not replica count. Option C (automatic failover) is inherent to Business Critical. Option D (zone redundancy) is determined by the zoneRedundant property, not replica count.

Option B is correct. Zone redundancy for Business Critical creates multiple replicas across different availability zones within the same region. If one zone fails, one of the other replicas becomes the primary automatically.

Option A is wrong because zone redundancy does not involve a secondary region. Option C is wrong because the replicas are kept in sync synchronously, not asynchronously. Option D is wrong because the replicas are within the same region.

Options A, C, and D are correct. The seed type determines initial synchronization. The secondary type (readable/non-readable) affects performance but not data loss.

The failover group name is for management. Option B is wrong because secondary type does not affect data loss. Option E is wrong because it's part of the failover group name.

Option D is correct because auto-failover groups automatically fail over to the secondary region with automatic read-write endpoint switch. Option A is incorrect because failover is automatic if the grace period is exceeded. Option B is incorrect because automatic failover does not require manual initiation.

Option C is incorrect because read-only listeners are also updated automatically.

Option D is correct. Active geo-replication provides asynchronous replication with an RPO of a few seconds to a few minutes, and failover can be initiated manually within minutes, meeting the RTO and RPO. Option A is wrong because point-in-time restore does not provide a separate secondary region.

Option B is wrong because long-term retention is for archival, not DR. Option C is wrong because failover groups use geo-replication but the RPO is still asynchronous; the question asks for the feature, and geo-replication is the core.

Option B is correct because Business Critical tier uses Always On availability groups with synchronous replication, providing fast automatic failover within the region. Option A is incorrect because zone-redundant configuration adds zone resilience but not faster failover within a zone. Option C is incorrect because read scale-out does not provide failover.

Option D is incorrect because geo-replication is for cross-region failover.

Options A and D are correct. For zero data loss, you need synchronous replication. Business Critical with zone redundancy provides synchronous replicas within the same region with automatic failover.

Hyperscale with zone redundancy also provides synchronous replicas for the log service. Option B (General Purpose) uses asynchronous replication and does not guarantee zero data loss. Option C (active geo-replication) is asynchronous, so data loss can occur.

Option E (failover groups) relies on geo-replication which is asynchronous.

Options A and D are correct. Failover groups provide a single endpoint for read/write and allow a readable secondary. Option B is incorrect because it does not provide built-in load balancing.

Option C is incorrect because TDE is not related to failover groups. Option E is incorrect because failover groups do not provide synchronous replication; they use asynchronous.

Options A and D are correct. Failover groups provide automatic failover and support readable secondary. Manual failback is possible by initiating a failover in the opposite direction.

Option B (active geo-replication) is not for managed instances. Option C (geo-restore) does not provide automatic failover. Option E (log shipping) is not built-in.

Option C is correct because the Business Critical tier with zone redundancy provides an SLA of 99.995% and automatic recovery from zone failures. Option A (General Purpose with zone redundancy) has a lower SLA (99.99%). Option B (Hyperscale with zone redundancy) offers 99.95% SLA for zone-redundant configuration.

Option D (Basic tier) does not support zone redundancy and has a lower SLA.

Option B is correct. General Purpose tier provides built-in high availability with automatic failover to a standby replica during patching events. This is a standard feature.

Option A is wrong because General Purpose does not have zone-redundant replicas by default. Option C is wrong because the database is not offline; it fails over seamlessly. Option D is wrong because manual failover is not required; it's automatic.

Option B is correct because SQL Managed Instance supports failover groups, which provide automated failover and readable secondary instances. Geo-replication is not supported for Managed Instance. Option A is wrong because geo-replication is not supported.

Option C is wrong because the secondary in a failover group is readable. Option D is wrong because log shipping is not supported.