The correct answer is A. IaC . Infrastructure as Code is used to define and deploy infrastructure through templates, configuration files, or code rather than building everything manually. During a cloud migration, that approach helps keep deployments consistent across environments and reduces the chance of human error.
This fits the question especially well because it mentions consistency, reliability, and efficiency in both provisioning and management. Those are exactly the kinds of benefits IaC is meant to provide. Instead of configuring servers, networks, and services one by one, administrators can reuse tested deployment definitions and apply the same settings repeatedly. That makes rollouts faster and easier to audit.
The other options do not match the task. A CDN improves content delivery performance. SASE is a networking and security architecture. ZTA focuses on access control and trust decisions. All of those are important in the right context, but none is primarily a provisioning and management automation tool.
In a cloud migration, the organization usually wants repeatable builds, standardization, and faster recovery if something has to be recreated. That is why IaC is the strongest answer here. It directly supports automated, dependable, and scalable infrastructure deployment.

This process describes Zero-touch provisioning (ZTP), where a device automatically pulls its configuration from a cloud controller or URL once connected to the internet. It's common in SD-WAN and modern network appliances.
A). SASE (Secure Access Service Edge) refers to cloud-delivered network security, not a provisioning method.
C). Infrastructure as code automates infrastructure deployment using code, but this scenario specifically fits ZTP.
D). Configuration management tracks and maintains system configurations but doesn't describe the installation process.
# Reference:
CompTIA Network+ N10-009 Official Objectives: 4.3 - Explain remote access methods and automation.

The correct answer is A. To support voltage requirements for devices in an IDF. In the CompTIA Network+ N10-009 objectives, network infrastructure includes power systems such as Uninterruptible Power Supplies (UPS) and Power Distribution Units (PDU), which are critical components in both MDF (Main Distribution Frame) and IDF (Intermediate Distribution Frame) environments.
A UPS provides temporary backup power during electrical outages and also conditions power by protecting against surges, spikes, and voltage fluctuations. This ensures that sensitive network equipment such as switches, routers, and servers can continue operating or safely shut down. A PDU, on the other hand, distributes electrical power to multiple devices within a rack, ensuring that all equipment receives the appropriate voltage and sufficient power capacity.
Option B is incorrect because while PDUs can help distribute power, they do not directly manage or optimize power consumption. Option C refers to networking devices like switches, not power equipment. Option D relates to environmental controls such as HVAC systems, not UPS or PDU devices.
Therefore, the primary purpose of UPS and PDU systems is to ensure stable and adequate power delivery to network devices, particularly in environments like IDFs.

Adding more access points can improve coverage, but it also increases the risk of co-channel interference if APs are configured on the same or overlapping channels. Channel overlap causes contention and interference, leading to retries, unstable performance, and symptoms that feel like frequent disconnect/reconnect events- especially in dense deployments. Network+ (N10-009) wireless troubleshooting objectives highlight proper channel planning (non-overlapping channels, appropriate channel width) as critical when increasing AP density. If adjacent APs are competing on the same channel (or overlapping channels in 2.4 GHz), clients may experience poor signal-to-noise ratios and repeated reassociations as they struggle to maintain a stable link.
Roaming misconfiguration can cause sticky clients or poor handoffs, but the classic problem introduced immediately after "adding more APs" is interference from bad channel design. Throughput capacity is about available bandwidth and airtime efficiency; it can make things slow, but it doesn't inherently cause repeated disconnect/reconnect loops like interference does. Packet loss is a symptom that may occur due to interference, but the root cause in the options that best fits the scenario is channel overlap.