Which two actions must be completed before starting the process of sending IoT data to the cloud via edge routers? (Choose two.)

Question

Options

• AMeasure the voltage, power rating, and quiescent current for the sensors that send data to the
• BGather the hardware (MAC) addresses of local and cloud routers to ensure low latency
• CCollect information about the CPU architecture in the cloud and edge to ensure that they match.
• DGather the interval, the volume, and the latency that the data must be provisioned with.
• ECollect information about growth, required elasticity, and high availability of the provisioning

• A
  5% (2)
• B
  2% (1)
• C
  9% (4)
• D
  84% (37)

Explanation

Before provisioning IoT data flows, you must first define the data requirements (D) - knowing the transmission interval, data volume, and acceptable latency tells you exactly what the pipeline must support. You also need capacity and resilience requirements (E) - understanding expected growth, how the system must scale (elasticity), and uptime guarantees (high availability) is essential for designing cloud infrastructure that won't fail under real-world conditions. Together, D and E capture the "what and how much" of provisioning before a single packet is configured.

Why the distractors are wrong:

• A is wrong because voltage, power ratings, and quiescent current are electrical sensor characteristics - relevant to hardware setup, not cloud data provisioning.
• B is wrong because MAC addresses are Layer 2 and do not traverse the internet; they're meaningless for cloud routing and low latency planning.
• C is wrong because cloud platforms abstract hardware differences - CPU architecture matching between edge and cloud is not a provisioning prerequisite.

Memory tip: Think "D = Data specs, E = Expansion specs" - you must define what your data looks like now (interval, volume, latency) and how it will grow over time (elasticity, HA) before you can provision anything correctly.

No community discussion yet for this question.