If a domain controller fails in an Active Directory environment, what happens next?

If a domain controller fails in an Active Directory environment, what happens next?

• A. Another domain controller automatically takes over its responsibilities
• B. The domain becomes read-only
• C. Local user accounts are deleted
• D. DNS entries are permanently removed

Answer: (A)

Active Directory is designed for redundancy by having multiple domain controllers that hold replicated copies of the directory. When one domain controller fails, other domain controllers automatically handle authentication and directory service requests, so users can continue to log in and access resources without manual intervention. Clients find available DCs via DNS, and requests are serviced by any online DC. The only time you’d need manual action is if the failed DC held a single-master FSMO role; in that case, roles would need to be seized on a remaining DC to avoid disruption. The domain does not become read-only, and DNS entries or user accounts are not permanently removed because of a single DC failure.

Active Directory is designed for redundancy by having multiple domain controllers that hold replicated copies of the directory. When one domain controller fails, other domain controllers automatically handle authentication and directory service requests, so users can continue to log in and access resources without manual intervention. Clients find available DCs via DNS, and requests are serviced by any online DC. The only time you’d need manual action is if the failed DC held a single-master FSMO role; in that case, roles would need to be seized on a remaining DC to avoid disruption. The domain does not become read-only, and DNS entries or user accounts are not permanently removed because of a single DC failure.