HCIP-IoT study plan

Map the four-layer IoT reference architecture (perception, network, platform, application) and label where gateways, LPWAN radios, and platform services sit in it

Draw from memory the OceanConnect/IoTDA device onboarding flow from product creation through profile definition, codec selection, and device registration

Distinguish device profile, product model (service/characteristic/property/command), and codec plugin, and state which artifact changes when a sensor adds a new telemetry field

Explain the difference between device-level and product-level management operations in IoTDA and list three operations that can be batched at product level

Configure a complete device lifecycle in a trial IoTDA instance: register a device, simulate telemetry with MQTT over TLS, issue a command, and deregister it

Compare MQTT, HTTP, and CoAP from the perspective of IoTDA device access, stating for each the transport, typical payload pattern, and suitability for battery-powered nodes

Describe how IoTDA rules engine and data forwarding push device data to a message broker or storage service, and identify where subscription topics are configured

Explain device shadow desired/reported state and demonstrate one scenario where the shadow prevents a command from being lost during disconnection

Outline OTA upgrade management in IoTDA: package creation, version targeting, and upgrade task monitoring

Compare ZigBee, Wi-Fi, Bluetooth/BLE, and RFID on range, data rate, power profile, topology, and typical IoT role, and place each in a comparison table

Trace a ZigBee network join sequence (permit-join, association, key transport) and explain the roles of coordinator, router, and end device

Explain BLE GATT structure (service, characteristic, descriptor) and how a gateway reads a notify-based sensor value

Describe RFID tag classes and the anti-collision problem when many tags respond in one reader field

Design the gateway northbound/southbound split for a BLE sensor fleet, stating which protocol carries data to the platform and why

Compare NB-IoT, eMTC/LTE-M, and LoRa on bandwidth, latency, mobility, voice support, coverage extension, and battery life, and justify each choice with a use case

Explain NB-IoT physical layer essentials: 180 kHz bandwidth, coverage enhancement repetitions, PSM and eDRX power-saving states, and the resulting trade-off between latency and battery life

Describe LoRa modulation (chirp spread spectrum), spreading factor versus data rate versus range, and LoRaWAN device classes A, B, and C

Calculate link budget or airtime for a given spreading factor and payload, and interpret whether a duty-cycle limit is respected

Explain how an NB-IoT or LoRa device attaches through a gateway or base station to reach the IoT platform, and where the protocol translation happens

Describe the edge computing reference model (device, edge gateway, cloud) and state three functions that must run at the edge rather than in the cloud, with the reason for each

Explain LiteOS kernel features: task scheduling, memory management, and the sensor/communication frameworks, and identify which components are optional in a minimal build

Compare running inference at the edge versus the cloud on latency, bandwidth, privacy, and model freshness, and pick a side for a video-analytics scenario

Outline how an edge node connects to IoTDA through a gateway, including local protocol conversion and store-and-forward during cloud outage

Enumerate the main IoT attack surfaces (device identity, onboarding, transport, platform API, firmware update) and match each to a concrete mitigation

Explain device authentication options in IoTDA (secret-based and certificate-based) and state when certificate-based mutual TLS is required

Describe secure boot and firmware signature verification on constrained devices, and explain why a failed verification must halt boot rather than warn

Identify common weaknesses in short-range links (default ZigBee keys, open BLE pairing, unauthenticated MQTT) and prescribe the fix for each

Draft a threat model for a smart-meter deployment covering at least five threats with likelihood, impact, and control

Decompose three solution scenarios (smart home, smart agriculture, connected vehicle or industrial monitoring) into perception, network, platform, and application layers with named technologies

Select gateway hardware class and connectivity for each scenario and justify the choice against power, cost, and environmental constraints

Size a solution roughly: estimate device count, message rate, and daily data volume, and check whether the chosen access technology and platform tier can carry it

Identify the failure modes of each scenario and state the redundancy or fallback that the design includes

Re-derive the full comparison tables for short-range and LPWAN technologies from memory and correct any gaps against notes

Re-explain the IoTDA onboarding and command flow end to end without reference material

Review every previously wrong practice item and write the corrected reasoning for each

Complete two timed full-length mock sets and record per-domain accuracy to find remaining weak domains

Close remaining gaps by re-reading only the weak-domain notes and re-testing those domains