1. IoT Foundations, Terminology, and System Models

Introduction and Context

The Internet of Things (IoT) refers to the integration of identifiable physical entities with sensing, processing, communication, and actuation capabilities so that they can collect data, exchange information, and influence physical or digital processes. The term is deceptively simple. IoT is not merely a collection of connected devices, nor is it equivalent to wireless networking. It is an interdisciplinary systems phenomenon involving embedded computing, communication networks, cloud and edge platforms, data engineering, control theory, cybersecurity, human organizations, and the physical environment.

The significance of IoT lies in the transformation of previously passive objects into participants in information systems. A temperature sensor can report conditions; an industrial controller can alter a production process; a connected vehicle can coordinate with infrastructure; and a medical device can support clinical decisions. In each case, value emerges not from connectivity alone but from the relationship among the physical object, its environment, communication infrastructure, software services, data, users, and organizational objectives.

At doctoral level, IoT should therefore be studied as a class of sociotechnical and cyber-physical systems. The central research problem is not simply how to connect more devices. It is how to design trustworthy, scalable, interpretable, secure, and economically sustainable systems in which computational models interact with uncertain physical reality.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the historical development and conceptual boundaries of IoT.

2. Distinguish IoT from machine-to-machine communication, cyber-physical systems, wireless sensor networks, and related technologies.

3. Interpret the principal layers and functions of IoT reference models.

4. Classify IoT systems according to scale, criticality, mobility, ownership, and deployment environment.

5. Analyze the relationships among devices, networks, platforms, data, users, and physical processes.

6. Evaluate IoT value chains, architectural trade-offs, risks, and governance requirements.

7. Apply system-modeling ideas to an IoT case and identify appropriate technical and organizational choices.

From Connected Objects to Cyber-Physical Systems

The intellectual roots of IoT extend through several technological traditions. Embedded systems placed computation inside products and machines. Automatic identification technologies, including barcodes and radio-frequency identification, made physical objects digitally recognizable. Wireless sensor networks enabled distributed measurement in environments where wired infrastructure was costly or impractical. Telemetry and supervisory control systems allowed remote monitoring of industrial assets. The growth of Internet protocols, mobile networks, cloud computing, and inexpensive microcontrollers subsequently made large-scale interconnection more feasible.

Early machine-to-machine (M2M) systems typically connected machines for telemetry, remote control, or operational reporting. An electricity meter, for example, might transmit consumption readings to a utility through a dedicated network. M2M emphasizes communication between machines, often within a relatively closed and purpose-specific system. IoT is broader. It may include machines, people, software services, physical spaces, organizations, and open Internet-based ecosystems. M2M can therefore be regarded as an important predecessor or component of IoT rather than a complete synonym.

A cyber-physical system (CPS) integrates computational processes with physical processes through feedback. Sensors observe the physical world, software estimates state or evaluates rules, and actuators influence the environment. The physical process then changes, producing new observations. This feedback loop distinguishes many CPS applications from systems that merely collect data. An industrial robot, autonomous vehicle, infusion pump, and smart-grid controller are CPS examples because their computational decisions can affect safety, motion, energy flow, or human health.

IoT and CPS overlap substantially but have different emphases. IoT traditionally emphasizes connectivity, identification, distributed information, and service ecosystems. CPS emphasizes timing, dynamics, control, and the coupling between computation and physical processes. A connected waste container that reports its fill level is an IoT application. A connected robotic system that continuously senses position and adjusts motion is both an IoT application and a CPS. The distinction is analytically useful because it reminds designers that not every IoT system requires closed-loop control, while systems involving physical feedback require stronger guarantees concerning timing, reliability, and safety.

Essential Terminology

An entity is any physical or logical participant represented within an IoT system. A thing is a physical object, environment, organism, or process that can be identified and integrated with digital services. Identification may be based on a network address, device identifier, digital certificate, RFID tag, or application-specific identity.

A sensor measures a physical property such as temperature, pressure, location, vibration, light, or chemical concentration. A transducer converts one form of energy or signal into another; sensors are a common class of transducer. An actuator converts a control signal into physical action, such as opening a valve, changing motor speed, or switching a relay.

A device is a deployable hardware-software unit that may sense, actuate, compute, communicate, or perform several of these functions. A device may be resource-constrained, such as a battery-powered sensor, or comparatively powerful, such as an industrial gateway.

A gateway connects devices or local networks to other networks and often performs protocol translation, aggregation, filtering, security enforcement, or edge analytics. An edge node performs computation close to the source of data. Fog computing refers to a distributed computing approach that places services across a continuum between devices and centralized cloud infrastructure.

A platform supplies reusable capabilities for device management, data ingestion, storage, processing, application integration, identity, and security. Platforms may be vendor-specific, open source, commercial, or hybrid. The term should not be treated as a guarantee of interoperability: a platform can simplify development while also creating dependency on a particular provider.

Telemetry is the collection and transmission of measurements from a remote location. Provenance records the origin, transformation history, and context of data. Digital twins are computational representations of physical entities or processes that are updated using observations and may support simulation, prediction, diagnosis, or control. A digital twin is more than a static digital record; its usefulness depends on synchronization, model validity, and the intended decision process.

Interoperability is the ability of heterogeneous systems to exchange and correctly use information. Syntactic interoperability concerns compatible data formats and protocols; semantic interoperability concerns shared meaning. Quality of service (QoS) describes performance characteristics such as latency, reliability, throughput, availability, and jitter. Quality of information (QoI) concerns the usefulness, accuracy, timeliness, completeness, and contextual validity of data.

A Layered Interpretation of IoT Systems

No single universal IoT architecture exists. Reference models are abstractions that help researchers and engineers reason about concerns, interfaces, and dependencies. A useful conceptual model contains six interacting layers.

The physical and device layer includes sensors, actuators, embedded processors, identification mechanisms, power supplies, and the physical objects or environments being observed. Design questions include measurement accuracy, calibration, energy consumption, physical security, operating temperature, maintenance, and tolerance of failure.

The connectivity layer provides local and wide-area communication. Technologies may include short-range radio, wireless personal-area networks, Wi-Fi, cellular systems, low-power wide-area networks, industrial fieldbuses, satellite links, or wired Ethernet. Protocol selection depends on range, energy, bandwidth, latency, mobility, spectrum conditions, cost, and regulatory constraints. Wireless connectivity is often convenient but introduces interference, propagation uncertainty, congestion, and exposure to eavesdropping or disruption.

The edge and gateway layer mediates between constrained devices and higher-level services. It can normalize protocols, remove duplicate readings, detect abnormal conditions, store data during outages, and execute time-sensitive control logic. Edge processing may reduce bandwidth and latency, but it creates additional software, update, and security responsibilities at distributed locations.

The platform and data layer manages device identities, data ingestion, storage, stream processing, metadata, rules, APIs, and digital models. Data may be processed as a real-time stream, stored for historical analysis, or combined with external sources. A technically sophisticated platform still fails if data lacks context, units, timestamps, calibration information, or a clearly defined owner.

The application and service layer turns data and control capabilities into domain functions, such as predictive maintenance, environmental monitoring, fleet management, smart buildings, remote healthcare, or agricultural optimization. Applications should be evaluated in relation to actual decisions and workflows rather than dashboards alone.

The governance and human layer cuts across all other layers. It includes users, operators, owners, regulators, communities, organizational processes, policies, ethics, accountability, and economic arrangements. This cross-cutting layer is essential because IoT systems alter responsibilities and may affect people who neither purchased nor directly operate the devices.

A second, complementary view is the device–network–platform–application model. It is simpler and useful for architectural communication, while the six-layer model exposes data, governance, and edge concerns more explicitly. Models should be selected according to the question being investigated. A model is a reasoning instrument, not a physical law.

System Taxonomies and Design Space

IoT systems can be classified along several dimensions. The first is the degree of human involvement. In human-in-the-loop systems, people interpret information or authorize actions. In human-on-the-loop systems, automation acts within approved boundaries while people supervise exceptions. In human-out-of-the-loop systems, decisions are largely automated, which may be appropriate for routine control but raises stronger requirements for verification, fail-safe behavior, and accountability.

A second dimension is operational criticality. Noncritical monitoring may tolerate delayed or missing data. Industrial safety, medical devices, transport control, and energy infrastructure may require bounded latency, high availability, redundancy, and formal risk analysis. Connectivity alone does not determine criticality; the consequences of failure do.

A third dimension is the system’s spatial and organizational scale. A personal-area system may contain wearable devices associated with one individual. An enterprise system may connect facilities, assets, and business applications. A city-scale system can involve multiple authorities, suppliers, communication networks, and public stakeholders. As scale increases, identity management, data governance, interoperability, and ownership become more difficult.

Mobility provides another classification. Fixed systems include building sensors and industrial installations. Nomadic systems are moved occasionally, whereas mobile systems such as vehicles, drones, and wearables change network attachment and operating conditions frequently. Mobility affects handover, localization, energy use, topology, and security assumptions.

IoT systems may also be event-driven or periodic, centralized or distributed, open or closed, and monitoring-oriented or control-oriented. A periodic environmental station may transmit a measurement every fifteen minutes. An event-driven alarm system may communicate only when a threshold or learned anomaly occurs. A centralized design can simplify management, while a distributed design may improve resilience and responsiveness. These are trade-offs rather than universally superior choices.

Data, Feedback, and System Behavior

The central IoT data path can be described as:

physical phenomenon → sensing → communication → interpretation → decision → actuation or service → changed physical state.

Each transition can introduce uncertainty. Sensors may be biased or poorly calibrated. Networks may delay or lose messages. Data models may misinterpret units or timestamps. Analytics may produce false positives. Operators may misunderstand a visualization. Actuators may fail, or a correct command may be unsafe under unusual conditions.

For this reason, IoT architecture should distinguish observation from knowledge and knowledge from action. A measurement is not automatically information; it becomes meaningful when associated with context. A prediction is not automatically a decision; it must be evaluated against cost, risk, authority, and alternatives. Similarly, an automated action should have defined operating limits, override mechanisms, and recovery behavior.

A useful systems perspective treats state estimation as an explicit concern. The physical state of a system is often only partially observable. Designers combine current sensor readings, historical data, domain models, and uncertainty estimates to infer conditions. This is particularly important in predictive maintenance, autonomous systems, and smart infrastructure. Research questions include how to quantify uncertainty, how to detect sensor drift, and how to maintain model validity when the environment changes.

The IoT Value Chain and Organizational Context

An IoT value chain begins with the physical asset and extends through sensing, connectivity, data management, analytics, application services, operational decisions, and measurable outcomes. Hardware manufacturers may supply sensors or gateways; network operators provide connectivity; platform providers manage device and data services; system integrators combine components; application vendors deliver domain solutions; and organizations use the resulting insights or automation.

Value is not created uniformly at every stage. A low-cost sensor may produce little value if its data cannot be trusted or integrated into a work process. Conversely, a modest amount of well-contextualized data can support substantial operational improvement. The economically relevant outcome might be reduced downtime, improved safety, lower energy use, better service quality, regulatory compliance, or a new product-service model.

The value chain also creates dependencies. An organization may depend on a cloud provider’s APIs, a network operator’s coverage, a device manufacturer’s firmware support, and a systems integrator’s specialized knowledge. These dependencies create risks of vendor lock-in, service discontinuity, incompatible updates, and unclear responsibility. Procurement should therefore consider data portability, API openness, lifecycle support, security obligations, and exit strategies.

Practical Architecture Method

A disciplined IoT design begins with the operational problem rather than with a preferred device or platform. The following sequence is useful for research and professional projects:

1. Define the decision or physical intervention that the system must improve.

2. Identify stakeholders, assets, environments, constraints, and failure consequences.

3. Specify what must be observed, at what accuracy, frequency, and latency.

4. Select sensing, actuation, identity, connectivity, edge, and platform functions.

5. Define data semantics, ownership, retention, interfaces, and quality requirements.

6. Analyze threats, privacy impacts, safety hazards, and regulatory obligations.

7. Design deployment, monitoring, maintenance, firmware updates, and decommissioning.

8. Validate the system through pilots, simulation, testing under adverse conditions, and operational feedback.

This process prevents a common error: treating deployment as the end of the project. IoT systems operate over long lifecycles. Batteries require replacement, sensors drift, networks evolve, certificates expire, vulnerabilities are discovered, and organizational processes change. Lifecycle engineering is therefore part of architecture, not an afterthought.

Illustrative Case: Connected Cold-Chain Monitoring

Background

Consider an illustrative case involving a regional pharmaceutical distributor. Temperature-sensitive medicines move from a central warehouse through refrigerated vehicles to clinics. The organization wishes to reduce spoilage and improve evidence that storage conditions remained within approved limits.

Situation and Problem

The existing process uses manual temperature checks at selected points. Readings are incomplete, alarms may be noticed late, and responsibility is disputed when a shipment is rejected. The organization initially proposes placing a wireless sensor in every container and sending all measurements directly to a cloud dashboard.

Analysis

The proposal addresses measurement but not the complete system problem. The design must specify calibration, sampling frequency, time synchronization, local storage during network outages, shipment identity, acceptable thresholds, alarm escalation, and chain-of-custody records. It must also distinguish a temporary temperature excursion from a sensor fault. Because vehicles may pass through areas with intermittent connectivity, continuous cloud availability cannot be assumed.

The system is an IoT application and a limited CPS: it primarily monitors conditions, but it may also control refrigeration equipment or trigger operational intervention. Its criticality is higher than that of ordinary asset tracking because incorrect data may affect product safety and regulatory compliance.

Approach and Solution

The distributor deploys calibrated sensors with secure device identities and tamper-evident enclosures. A vehicle gateway collects readings, validates timestamps, stores data locally during connectivity loss, and forwards prioritized alarms when a connection becomes available. The cloud platform maintains shipment, sensor, vehicle, and location relationships. An analytics service detects sustained excursions and sensor anomalies rather than relying solely on a single threshold crossing.

Role-based access controls separate drivers, warehouse staff, quality personnel, and auditors. The application presents an evidence timeline showing measurements, connectivity gaps, interventions, and custody transfers. Firmware updates are signed, and devices have a documented replacement and calibration schedule.

Outcome

The illustrative organization gains earlier awareness of excursions and a more defensible record for quality investigations. The main improvement does not arise from the dashboard itself. It arises from integrating trustworthy measurements with shipment identity, exception workflows, maintenance procedures, and accountability. The case also demonstrates that edge storage, data provenance, and governance can be as important as radio range or cloud analytics.

Learning Points

The case emphasizes five principles: requirements should be tied to decisions; data requires context and provenance; intermittent connectivity must be designed for; security and quality assurance are lifecycle activities; and value is realized through organizational action, not connectivity alone.

Challenges, Risks, and Limitations

Interoperability is difficult because devices may use incompatible protocols, data formats, identity schemes, and semantic models. Standards can reduce friction, but standards adoption does not automatically ensure compatible implementations.

Scalability involves more than the number of devices. It includes message volume, certificate management, firmware distribution, observability, storage, support processes, and the ability to diagnose failures across heterogeneous deployments.

Energy constraints shape sensing frequency, radio use, computation, and maintenance. Aggressive power saving may reduce data quality or responsiveness. Energy harvesting can help in some environments but introduces its own variability.

Reliability and uncertainty arise from sensor drift, radio interference, environmental damage, network outages, software faults, and inaccurate models. Redundancy, calibration, confidence measures, graceful degradation, and human escalation are possible responses.

Security exposure increases as physical devices and gateways become attack surfaces. Weak credentials, insecure update mechanisms, excessive privileges, exposed interfaces, and unsupported legacy devices are common weaknesses. Security must include prevention, detection, response, recovery, and retirement.

Privacy risks may emerge even when a system was not designed to collect personal information. Location traces, occupancy patterns, health readings, voice data, and inferred behavior can identify or profile individuals. Data minimization and purpose limitation should guide collection.

A frequent design mistake is to treat a dashboard as the solution. Visualization can reveal conditions, but it does not define authority, automate a safe response, or repair a broken process. Another mistake is to optimize technical metrics while ignoring total cost of ownership, field maintenance, workforce acceptance, and organizational incentives.

Ethics, Governance, and Regulation

IoT governance determines who may collect data, who owns it, who may access it, how long it is retained, and who is accountable when an automated decision causes harm. Meaningful governance requires documented purposes, proportional data collection, access controls, auditability, transparent notices, and processes for correction or deletion where applicable.

Safety-critical deployments should separate convenience functions from essential protection functions. A cloud service may support monitoring, but a local safety interlock may be necessary when communication fails. Automated decisions should be explainable to the extent required by their consequences, and human oversight should be substantive rather than merely nominal.

Professional practice also requires consideration of affected non-users. A smart building may infer occupancy patterns of employees; a connected street system may monitor public movement; agricultural sensors may alter labor practices. Ethical analysis should therefore include communities, workers, vulnerable populations, and environmental effects, not only the purchasing organization.

Current Developments and Research Directions

Several developments are reshaping IoT research and practice. Edge and federated approaches seek to reduce latency, bandwidth use, and unnecessary centralization of data. Artificial intelligence supports anomaly detection, predictive maintenance, adaptive control, and sensor fusion, but model drift, explainability, adversarial manipulation, and energy cost remain significant concerns.

Digital twins are moving from descriptive visualization toward simulation, what-if analysis, and closed-loop optimization. Their credibility depends on model fidelity, synchronization, uncertainty representation, and governance of model changes. Interoperability research increasingly addresses semantic models, common APIs, digital identities, and cross-domain data spaces.

New wireless systems offer greater capacity, coverage, positioning, and device density, but connectivity improvements do not eliminate architectural questions. Low-power networks, private cellular systems, satellite connectivity, and integrated sensing and communication may expand deployment options. Research continues on trustworthy autonomy, sustainable device lifecycles, post-quantum security planning, resilient infrastructure, and the environmental cost of producing, powering, and disposing of connected devices.

Best-Practice Principles

A robust IoT program should:

• begin with a measurable operational or societal objective;
• model physical, digital, organizational, and human relationships together;
• use standard interfaces and explicit data semantics where feasible;
• assign identity and least privilege to devices, users, and services;
• design for outages, uncertainty, maintenance, and secure updates;
• keep safety-critical functions locally enforceable when necessary;
• measure data quality and decision outcomes, not only connectivity;
• evaluate privacy, accessibility, environmental impact, and inclusion;
• plan procurement, portability, decommissioning, and long-term support;
• validate assumptions through field evidence rather than laboratory performance alone.

Chapter Summary

IoT is an interdisciplinary system of physical entities, computation, communication, data, services, people, and environments. Its historical development draws on embedded systems, identification technologies, wireless sensor networks, telemetry, M2M communication, cloud computing, and cyber-physical systems. IoT is broader than M2M, while CPS highlights feedback, timing, and physical consequences.

Layered reference models help analyze devices, connectivity, gateways and edge computing, platforms and data, applications, and governance. Taxonomies based on criticality, scale, mobility, human involvement, openness, and control orientation reveal important design trade-offs. The IoT value chain extends from physical observation to interpretation, decision, intervention, and organizational outcomes. Successful systems require trustworthy data, interoperability, lifecycle security, privacy protection, resilience, and clear accountability. Emerging work in edge intelligence, digital twins, advanced wireless systems, and autonomous decision-making increases capability while also intensifying questions of uncertainty, governance, sustainability, and ethics.

Key Terms

Actuator: A component that converts a control signal into physical action.

Cyber-physical system: A system in which computational processes interact with and influence physical processes through sensing and control.

Digital twin: A dynamic computational representation of a physical entity or process, updated with relevant observations.

Edge computing: Processing performed near the source of data to reduce latency, bandwidth use, or dependence on centralized services.

Entity: A physical or logical participant represented within an IoT system.

Gateway: An intermediary that connects local devices or networks to other networks and may translate protocols or process data.

Interoperability: The ability of different systems to exchange and correctly use information.

Internet of Things: An ecosystem of identifiable physical entities, computing, communication, data, and services that interact with physical or digital environments.

Machine-to-machine communication: Direct or automated communication between machines, commonly for monitoring or control.

Quality of information: The accuracy, timeliness, completeness, relevance, and contextual usefulness of data.

Quality of service: Communication or service performance characteristics such as latency, reliability, availability, and throughput.

Sensor: A device or component that measures a physical property and produces a corresponding signal or data value.

Telemetry: The remote collection and transmission of measurements.

Thing: A physical object, organism, environment, or process represented and connected within an information system.

Transducer: A device that converts energy or a signal from one form to another.

Value chain: The linked activities through which sensing, connectivity, data, services, and decisions produce organizational or societal value.

Wireless sensor network: A distributed collection of sensor nodes that communicate wirelessly to observe physical conditions.

Provenance: Information describing the origin, history, transformations, and context of data.

Review Questions

Short Answer Questions

1. How does IoT differ conceptually from machine-to-machine communication?

2. What distinguishes a cyber-physical system from a system that only monitors conditions?

3. State two functions commonly performed by an IoT gateway.

4. Why is semantic interoperability important in IoT systems?

5. What is meant by quality of information?

Long Answer Questions

1. Explain the evolution from embedded systems and telemetry to IoT, distinguishing the contributions of M2M and CPS.

2. Describe and critically evaluate the six-layer IoT reference model presented in this chapter.

3. Discuss how scale, mobility, criticality, and human involvement influence IoT architecture.

4. Analyze the IoT value chain and explain why connectivity alone does not guarantee value creation.

5. Explain the principal security, privacy, lifecycle, and governance requirements of a large IoT deployment.

Analytical / Application Questions

1. A water utility wants to monitor pressure across a city and automatically close valves during suspected pipe bursts. Classify the system and propose an architecture, including edge functions, connectivity, data governance, and fail-safe behavior.

2. An organization receives accurate sensor readings but cannot determine which shipment, device, or calibration period each reading relates to. Diagnose the architectural deficiencies and recommend corrective measures.

3. Compare a centralized cloud design with an edge-distributed design for an autonomous warehouse robot system. Evaluate latency, resilience, security, maintenance, and organizational trade-offs.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes IoT from traditional machine-to-machine communication?

A. IoT uses only wireless networks, whereas M2M uses wired networks.

B. IoT is broader and may integrate devices, people, platforms, organizations, and open services, whereas M2M commonly describes purpose-specific machine communication.

C. M2M always includes physical actuation, whereas IoT is limited to monitoring.

D. IoT requires cloud computing, whereas M2M cannot use cloud services.

Correct Answer: B. IoT is broader and may integrate devices, people, platforms, organizations, and open services, whereas M2M commonly describes purpose-specific machine communication.

Question 2

Why is a cyber-physical system more than a data-collection system?

A. It necessarily uses cellular communication.

B. It requires a public Internet address for every sensor.

C. Its computational processes interact with physical processes through feedback and may influence physical behavior.

D. It stores all measurements permanently in a cloud database.

Correct Answer: C. Its computational processes interact with physical processes through feedback and may influence physical behavior.

Question 3

Which function is most appropriately associated with an IoT gateway?

A. Replacing every physical sensor with a software model.

B. Performing protocol translation, local filtering, and temporary storage during connectivity outages.

C. Guaranteeing that all data is semantically correct without metadata.

D. Eliminating the need for device identity and authentication.

Correct Answer: B. Performing protocol translation, local filtering, and temporary storage during connectivity outages.

Question 4

A temperature reading without units, timestamp, sensor identity, or calibration context is primarily deficient in which respect?

A. Physical actuation

B. Data provenance and quality of information

C. Radio transmission power only

D. Application user-interface design only

Correct Answer: B. Data provenance and quality of information

Question 5

Which architectural choice is most appropriate for a safety-critical control function when network connectivity may fail?

A. Make the control function dependent entirely on a remote cloud service.

B. Disable local sensing to reduce system complexity.

C. Keep essential protection or control logic locally enforceable, while using remote services for monitoring and coordination.

D. Use an un authenticated broadcast channel to minimize latency.

Correct Answer: C. Keep essential protection or control logic locally enforceable, while using remote services for monitoring and coordination.

Question 6

In the cold-chain case, why was local gateway storage important?

A. It increased the physical accuracy of the sensor.

B. It allowed data to be retained and forwarded when vehicle connectivity was intermittent.

C. It removed the need for shipment identification.

D. It guaranteed that refrigeration equipment could never fail.

Correct Answer: B. It allowed data to be retained and forwarded when vehicle connectivity was intermittent.

Question 7

Which statement best describes semantic interoperability?

A. Systems use the same physical cable.

B. Systems exchange data at the same transmission speed.

C. Systems share or correctly interpret the meaning of exchanged data.

D. Systems are manufactured by the same company.

Correct Answer: C. Systems share or correctly interpret the meaning of exchanged data.

Question 8

An organization evaluates an IoT project only by counting connected devices. What important issue is it most likely neglecting?

A. Whether the system produces trustworthy information and improves decisions or outcomes.

B. Whether sensors contain any processors.

C. Whether all devices are physically identical.

D. Whether wireless signals exist anywhere in the world.

Correct Answer: A. Whether the system produces trustworthy information and improves decisions or outcomes.

Question 9

Which characteristic most strongly increases the governance and accountability requirements of an IoT system?

A. The use of a small battery.

B. The possibility that automated actions affect health, safety, rights, or essential infrastructure.

C. The presence of a dashboard with multiple colors.

D. The use of periodic rather than event-driven measurements.

Correct Answer: B. The possibility that automated actions affect health, safety, rights, or essential infrastructure.

Question 10

What is the principal purpose of a digital twin in an IoT context?

A. To provide a static inventory label that never changes.

B. To represent a physical entity or process dynamically using observations for monitoring, prediction, simulation, or control.

C. To replace all physical testing regardless of model uncertainty.

D. To encrypt radio signals without requiring keys.

Correct Answer: B. To represent a physical entity or process dynamically using observations for monitoring, prediction, simulation, or control.