Multi-factor authentication requires more than one way to verify who you are, which makes it much harder for someone to pose as you. It uses at least two independent factors, typically something you know (like a password), something you have (a code from a device or an app), or something you are (a fingerprint or other biometric). By needing multiple proofs, even if one factor is compromised, access isn’t granted without the other factors. That’s why the statement that best describes MFA is that it uses multiple verification methods to increase security. The other ideas fall short because a single verification method is just single-factor authentication, the acronym reference is incorrect, and MFA isn’t limited to only high-security environments; it’s common in everyday security practices.

Disaster recovery planning focuses on how to resume operations after a disruption, balancing data protection with timing. The best answer includes defining the Recovery Time Objective and Recovery Point Objective, which set the maximum allowable downtime and data loss, guiding how you design backups and replication. Backups provide the actual data copies you restore from, while failover plans describe how to switch to an alternate system or site to keep services running. Testing is crucial to verify that the plan works, that backups are usable, and that failover procedures will execute smoothly during an incident. Together, these elements establish the targets for recovery and the concrete steps to meet them. The other options cover general IT operations rather than the specific components needed to recover from a disaster. Service-level agreements, maintenance windows, change management, and runbooks relate to service expectations and process control. Asset tags, SAMPLEinventory, lifecycle, and maintenance focus on asset management. SNMP, monitoring, and performance deal with detecting and measuring system health, not the actual recovery strategy.

Change control is about governing changes to IT systems so that every modification goes through a formal, reviewed process. This means proposed changes are evaluated for risk, tested in a safe environment, approved by responsible stakeholders, scheduled to minimize impact, and backed up with a plan to roll back if something goes wrong. By inserting checks and oversight, change control reduces the chance that a risky or unapproved modification will cause outages, performance problems, or security gaps. That’s why this option is the best. It captures the core purpose: preventing unapproved or risky changes that could jeopardize availability or security. The other ideas miss the broader role of change control: it isn’t solely about speed, it isn’t just about documenting topology, and it isn’t limited to security updates. Change control applies to all meaningful changes, with governance, testing, and rollback planning to protect the environment.

A records are used to map a domain name to an IPv4 address. This is the standard way a hostname is resolved for IPv4 networks, linking something like a domain to a 32-bit address such as 198.51.100.5. The other record types serve different purposes: AAAA records map a domain to an IPv6 address, CNAME records create an alias from one name to another domain name, and MX records specify which mail server handles email for the domain. So when the goal is to find the IPv4 address associated with a domain, the A record is the one that provides that mapping.