DP-300 Plan and configure high availability and disaster recovery • Complete Question Bank
Complete DP-300 Plan and configure high availability and disaster recovery question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit.
```
-- Current state of the availability group
SELECT ag.name AS ag_name,
replica_server_name,
role_desc,
operational_state_desc,
connected_state_desc,
synchronization_health_desc,
last_connect_error_number,
last_connect_error_time
FROM sys.dm_hadr_availability_replica_states rs
JOIN sys.availability_groups ag ON rs.group_id = ag.group_id
WHERE ag.name = 'AG1';
```
Output:
ag_name | replica_server_name | role_desc | operational_state_desc | connected_state_desc | synchronization_health_desc | last_connect_error_number | last_connect_error_time
AG1 | SQLVM-Primary | PRIMARY | PENDING_FAILOVER | CONNECTED | HEALTHY | 0 | NULL
AG1 | SQLVM-Secondary | SECONDARY | ONLINE | DISCONNECTED | NOT_HEALTHY | 35202 | 2024-03-15 10:30:00.000Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Encrypts data at rest
Encrypts sensitive data in transit and at rest
Limits exposure of sensitive data by masking it to non-privileged users
Restricts access to rows based on user characteristics
Drag a concept onto its matching description — or click a concept then click the description.
Service is busy; retry the request later
Database is not currently available
Cannot open server '%.*ls' requested by the login
Login failed for user
Error log excerpt: 2025-03-15 14:23:45.67 Error: 406, Severity: 16, State: 0. The database 'OrdersDB' has an automated backup frequency of 12 hours and a point-in-time restore (PITR) retention period of 7 days. The long-term retention (LTR) policy is configured as: - Weekly: Sunday 02:00, retention 4 weeks - Monthly: First Sunday 02:00, retention 12 months - Yearly: First Sunday of March 02:00, retention 3 years Current time: 2025-03-15 14:30 (Saturday) Last successful backup: 2025-03-15 02:00 Attempted restore to 2025-03-14 10:00 UTC failed with error 406.
Availability group configuration: AG1 (Synchronous commit) - Primary replica: SQL1 (automatic failover) - Secondary replica: SQL2 (automatic failover, readable secondary) - Secondary replica: SQL3 (synchronous commit, manual failover, readable secondary) Listener: listener1, port 1433 Error log on SQL1: 2025-03-15 15:00:00.00 spid31s The availability group 'AG1' is being restarted due to a failure. Error: 35201. A connection timeout has occurred. 2025-03-15 15:00:05.00 spid31s The local availability replica of availability group 'AG1' has transitioned from resolving role to primary role. 2025-03-15 15:00:10.00 spid31s The availability group 'AG1' is online. Query on SQL1: SELECT replica_server_name, role_desc, synchronization_health_desc, connected_state_desc FROM sys.dm_hadr_availability_replica_states WHERE group_id = '...' Results: SQL1 | PRIMARY | HEALTHY | CONNECTED SQL2 | SECONDARY | NOT_HEALTHY | DISCONNECTED SQL3 | SECONDARY | HEALTHY | CONNECTED