Digital and Physical Infrastructure

Introduction

Smart cities are often described as digital systems, but their intelligence depends on the interaction of digital technologies with physical assets. Roads, buildings, drainage networks, streetlights, water systems, construction sites and public facilities generate data and provide the environment in which digital services operate. Conversely, digital infrastructure enables these assets to be monitored, coordinated and optimized.

Digital and physical infrastructure should therefore be planned as one socio-technical system. A sensor without a reliable communication link produces little value; a data platform without trustworthy data can support poor decisions; and a highly automated system without safe physical design can amplify risk. For construction professionals, this relationship is particularly important because infrastructure projects increasingly include sensors, telecommunications equipment, control systems, geographic information systems and cloud-connected operational platforms.

This chapter examines the principal components of smart-city infrastructure: Internet of Things (IoT) sensors, communication networks, 5G, cloud and edge computing, geospatial infrastructure, data centers and urban platforms. It also explains the requirements of reliability, scalability, interoperability, cybersecurity, maintainability and governance.

Learning Objectives

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

1. Explain how IoT sensors collect and transmit data from urban assets.
2. Compare common communication technologies and identify suitable applications.
3. Describe the capabilities and limitations of 5G networks.
4. Distinguish cloud, edge and fog computing architectures.
5. Explain the role of geospatial infrastructure and digital twins.
6. Describe the functions of data centers and urban data platforms.
7. Evaluate infrastructure using reliability, scalability, latency, interoperability and security criteria.
8. Apply these concepts to the planning of a connected urban project.

1. Smart-City Infrastructure as a Layered System

A useful model divides smart-city infrastructure into interconnected layers:

The layers are not strictly sequential. A traffic signal, for example, may sense vehicle movement, process it locally, communicate with a control centre and respond through an actuator. The system may also publish selected information to a public mobility application.

A smart-city architecture should be assessed as an end-to-end service rather than as a collection of devices. Important questions include:

• What decision or service does the system support?
• What data are necessary, and at what frequency and accuracy?
• What happens if communications fail?
• Where should data be processed?
• Who owns, accesses and retains the data?
• Can equipment be replaced without redesigning the entire system?

This systems perspective prevents technology-led projects in which devices are installed without a clear operational purpose.

2. IoT Sensors and Actuators

The Internet of Things is a network of identifiable physical objects that can sense, communicate, compute or act. In cities, an IoT device may be a water-pressure sensor, air-quality monitor, smart meter, structural strain gauge, parking sensor or building automation controller.

2.1 Sensors

A sensor converts a physical quantity into a usable signal. Typical measured variables include temperature, humidity, pressure, acceleration, vibration, light, sound, flow, occupancy, location and chemical concentration. A sensor system normally includes:

1. A sensing element that responds to a physical phenomenon.
2. Signal conditioning, such as amplification or filtering.
3. An analogue-to-digital converter where the signal is analogue.
4. A processor or gateway that formats and evaluates readings.
5. A power source and enclosure.
6. A communication interface.

Important sensor characteristics include accuracy, precision, resolution, range, response time, drift, calibration stability and energy consumption. Accuracy describes closeness to the true value; precision describes repeatability. A sensor can be precise but inaccurate if it is systematically miscalibrated.

A basic measurement model can be written as:

Here, y is the observed measurement, x is the actual quantity, b is systematic bias and ε is random error. This model assumes that the measured value is represented adequately by an additive bias and random error. In practice, non-linear errors and environmental effects may also occur.

Calibration, environmental compensation and quality checks are therefore essential. A city should not treat every sensor reading as equally reliable. Metadata should record the device identity, location, unit, calibration date, firmware version and quality status.

2.2 Actuators and control

An actuator converts a command into physical action. Examples include motorized valves, traffic-signal controllers, pumps, heating systems and adjustable streetlights. Sensing and actuation form a control loop. The system observes a condition, compares it with a desired state, determines an action and measures the result.

Safety-critical control should not depend entirely on a remote cloud service. Local controllers should be able to maintain safe operation when communication is interrupted. For example, a flood-control pump may use local level thresholds even when its supervisory connection is unavailable.

2.3 Sampling and data volume

Sampling frequency should reflect the phenomenon being measured and the decision being made. A slowly varying water level may require measurements every several minutes, whereas vibration monitoring may require hundreds or thousands of samples per second. Excessive sampling increases energy use, network traffic and storage requirements without necessarily improving decisions.

If a sensor produces one record of size S bytes at frequency f records per second, the uncompressed data rate is:

where R is measured in bytes per second. For N identical sensors, assuming simultaneous continuous transmission and no protocol overhead, the aggregate rate is:

Real systems require additional allowance for headers, retransmissions, encryption, metadata and bursts. Video systems usually dominate bandwidth, while low-power environmental sensors generally generate modest volumes.

2.4 Power and maintenance

Battery-powered devices require a maintenance strategy. Battery life depends on sensing frequency, radio transmission power, processing load, temperature and battery characteristics. Duty cycling—keeping a device asleep except when it measures or communicates—can substantially reduce consumption. However, a device that is difficult to access may need a larger battery, energy harvesting or a lower reporting frequency.

The physical installation is as important as the electronics. Devices must be protected from water, dust, vandalism, electromagnetic interference and accidental damage. Construction documentation should identify mounting details, access clearances, cable routes, replacement procedures and responsibility for future maintenance.

3. Communication Networks

Communication networks connect devices, edge systems, control centres and users. Network selection should follow service requirements rather than popularity. Relevant criteria include coverage, bandwidth, latency, reliability, mobility, power consumption, ownership, installation cost and security.

A practical design often combines several technologies. Fibre may connect buildings and traffic cabinets; cellular networks may connect mobile assets; low-power networks may serve battery-operated meters; and Wi-Fi may support local operations.

3.1 Network performance

Latency is the time between an event and the receipt or processing of the corresponding information. It includes sensing, queuing, transmission, propagation and processing delays. Bandwidth is the maximum data-transfer capacity, whereas throughput is the actual achieved rate. Reliability concerns the probability that communication performs as required under specified conditions.

Availability is commonly expressed as:

where MTBF is mean time between failures and MTTR is mean time to repair or restore service. The equation assumes a repairable system in a steady operating condition and uses consistent time units. For example, if a service has an MTBF of 1,000 hours and an MTTR of 10 hours, then A = 1000 ÷ 1010 ≈ 0.9901, or approximately 99.01 percent. This is an operational availability estimate; it does not by itself capture scheduled maintenance, correlated failures or degraded performance.

Reliability and availability are related but different. Reliability often concerns successful operation over a specified interval without failure. Availability also considers how quickly service is restored after failure. A system can have frequent failures but high availability if repairs are very rapid, although that may be unacceptable for safety-critical services.

3.2 Network resilience

Resilience is the capacity to withstand, adapt to and recover from disruption. Measures include redundant links, diverse physical routes, backup power, alternative communication technologies, local autonomous operation, spare equipment and tested recovery procedures. Two cables in the same duct do not provide full path diversity because one excavation incident may damage both.

4. 5G in the Smart City

5G is a family of cellular technologies designed to improve capacity, responsiveness, mobility and device support compared with earlier generations. Its relevance to smart cities is not simply higher smartphone speed. Potential applications include connected vehicles, high-density sensor deployments, remote inspection, augmented-reality construction support and mobile public-safety systems.

Important capabilities include:

• Enhanced mobile broadband for high-throughput applications.
• Support for large numbers of connected devices.
• Reduced latency under suitable network conditions.
• Network slicing concepts that allow logically separated service characteristics.
• Improved management of mobile and temporary assets.

Actual performance depends on spectrum, radio frequency, site density, backhaul, building materials, network load, device capability and operator configuration. A 5G label does not guarantee a particular latency or availability. Critical infrastructure owners should specify measurable service levels rather than relying on technology names.

5G also introduces planning issues. Small cells may require access to poles, rooftops, street furniture and power. Permissions, visual impact, electromagnetic-exposure compliance, maintenance access and coordination with other utilities must be addressed. Construction teams should coordinate ducts, cabinets, equipment rooms and structural supports early in design.

5G is not a universal replacement for fibre, Wi-Fi or low-power networks. Fibre remains important for high-capacity fixed backhaul, and low-power networks may be more economical for simple battery-operated sensors. A sound architecture uses 5G where mobility, coverage or responsive wireless communication provides value.

5. Cloud, Edge and Fog Computing

5.1 Cloud computing

Cloud computing provides on-demand access to configurable computing resources, such as servers, storage, databases and analytics services. Resources are pooled, rapidly provisioned and commonly charged according to consumption or subscription. Cloud platforms support large-scale data aggregation, machine learning, application hosting, backup and collaboration.

Advantages include scalability, centralized management, broad accessibility and access to specialized services. Risks include dependence on connectivity, vendor lock-in, data-jurisdiction issues, recurring costs, cyberattack exposure and difficulty transferring legacy applications.

5.2 Edge computing

Edge computing places processing close to the source of data or the point of action. An edge device may be installed in a traffic cabinet, building, vehicle, construction site or local control room. Edge processing can reduce latency, lower bandwidth use, preserve privacy and allow continued operation during network outages.

Examples include detecting a dangerous machine condition locally, filtering video before transmission, controlling a pump using local rules, or recognizing occupancy without sending raw images to a central server.

5.3 Fog and hybrid architectures

Fog computing is commonly used to describe an intermediate distributed layer between edge devices and centralized cloud resources. In practice, terminology varies, and organizations should define architectural responsibilities clearly. A hybrid architecture may use:

• Device-level control for immediate safety functions.
• Edge processing for filtering and local decisions.
• Regional systems for coordination among nearby assets.
• Cloud platforms for historical analysis, cross-city optimization and long-term storage.

The location of computation should be decided using latency, bandwidth, privacy, resilience, cost and operational requirements. Raw data need not always be transmitted if a locally generated event, feature or summary is sufficient.

6. Geospatial Infrastructure and Digital Twins

Geospatial infrastructure enables data to be referenced to location, coordinate systems and time. It includes surveying control, satellite positioning, geographic information systems (GIS), remote sensing, spatial databases, address systems, 3D city models and standards for sharing geographic data.

Location is a common integration key. A sensor can be associated with a road segment, building, pipe, parcel or construction work package. However, location alone is insufficient. The system should also represent asset identity, ownership, condition, connectivity, elevation, time and uncertainty.

A GIS usually supports data capture, storage, analysis and visualization. Vector data represent discrete features such as parcels, roads and pipes; raster data represent continuous or regularly sampled surfaces such as satellite imagery, elevation or temperature. Coordinate reference systems must be documented because combining layers with incompatible datums or projections can produce positional errors.

A digital twin is a structured digital representation of a physical asset or system that is linked to current or historical data and supports a defined purpose. It is more than a 3D model. A useful urban digital twin may include geometry, asset identity, sensor streams, maintenance history, simulation models, permissions and links to operating procedures. The level of detail should match the decisions to be supported.

For construction, digital twins can connect building information models, schedules, inspection records, sensor data and facility-management systems. During operation, the twin may support energy analysis, space management, predictive maintenance or emergency planning. A model that is visually impressive but not updated, governed or connected to operational workflows is not an effective twin.

7. Data Centers and Urban Platforms

Data centers provide physical facilities and technical systems for computing and storage. Their design considerations include power supply, cooling, fire protection, physical security, network connectivity, equipment redundancy and environmental management. Urban systems may use large centralized facilities, regional facilities or smaller edge data rooms.

A data center’s resilience depends on the complete chain: utility power, generators, uninterruptible power supplies, cooling, network paths, hardware, software and staff procedures. Redundancy should be matched to service criticality. Duplicate equipment alone does not ensure resilience if both units share a single power distribution board or cooling failure mode.

Urban platforms integrate data and services across agencies and operators. Common functions include:

• Device registration and configuration.
• Identity and access management.
• Message ingestion and routing.
• Time-series and spatial data storage.
• Data quality monitoring.
• Application programming interfaces (APIs).
• Event processing and alerting.
• Dashboards and reporting.
• Digital-twin and simulation services.
• Audit logging and security monitoring.

An urban platform should not become an uncontrolled data lake. Data must have defined owners, quality rules, retention periods, access rights and intended uses. Data catalogues and metadata make information discoverable and interpretable.

8. Reliability, Scalability and Interoperability

8.1 Reliability engineering

Reliability requirements should be derived from consequences of failure. A public information display, a flood-warning system and an autonomous traffic-control function do not require identical service levels. Requirements may specify maximum outage duration, allowable data loss, response time, recovery time and safe failure behavior.

A simple series system, in which every component must operate for the service to operate, has reliability:

where Rᵢ is the reliability of component i, and the product applies when component failures are statistically independent and all components are required. For two independent components with reliabilities 0.99 and 0.98, system reliability is 0.99 × 0.98 = 0.9702. Real systems may have common-cause failures, so this calculation can overestimate performance.

For two independent components arranged in parallel, where at least one must work, the reliability is:

This formula assumes independence and identical mission conditions. Redundancy improves reliability only when failures are sufficiently independent and the switching or load-sharing mechanism works.

8.2 Scalability

Scalability is the ability to maintain acceptable service as demand grows. Growth may involve more sensors, users, geographic areas, data volume, applications or analytical complexity. Vertical scaling increases the capacity of an existing resource; horizontal scaling adds resources or instances.

Scalable design practices include stateless application services, partitioned databases, message queues, automated provisioning, elastic storage, caching and clear data-retention policies. Scaling must include operations, cybersecurity, staffing and physical facilities—not only server capacity.

A capacity model should distinguish average demand from peak demand. If a platform receives 10,000 messages per minute on average but 50,000 during an emergency, the peak governs ingestion, queueing and alerting design. Capacity tests should reproduce realistic bursts and failure conditions.

8.3 Interoperability

Interoperability is the ability of systems to exchange information and use the exchanged information effectively. It has several dimensions:

• Technical interoperability: devices and networks can connect.
• Syntactic interoperability: systems use compatible data structures.
• Semantic interoperability: terms and meanings are understood consistently.
• Organizational interoperability: institutions agree on processes, responsibilities and permissions.

Open standards, documented APIs, common identifiers, version control and data dictionaries support interoperability. In construction and facilities management, asset identifiers should persist across design, construction, commissioning and operation. Proprietary formats may be useful internally, but critical information should be exportable in documented, machine-readable forms.

9. Cybersecurity, Privacy and Governance

Connecting physical systems creates cyber-physical risk. An attack on a data dashboard may be inconvenient; an attack on a water-treatment controller, railway signal or building-management system may threaten safety. Security should therefore be designed from the beginning rather than added after installation.

Core practices include:

• Unique device identities and strong authentication.
• Least-privilege access.
• Encryption in transit and, where appropriate, at rest.
• Secure boot and signed firmware.
• Network segmentation between operational and corporate systems.
• Vulnerability management and patch planning.
• Logging, monitoring and incident response.
• Backups and tested recovery procedures.
• Secure decommissioning and credential revocation.

Privacy must be considered when systems collect location traces, video, biometric information, household consumption or other identifiable data. Data minimization means collecting only what is necessary for a legitimate purpose. Retention periods, access controls, anonymization or aggregation should be defined before deployment. Legal requirements vary by jurisdiction, so project teams must consult applicable data-protection, telecommunications, construction, safety and critical-infrastructure regulations.

Governance also concerns accountability. A city should know who is responsible for sensor calibration, platform operation, software updates, data correction, emergency decisions and public communication. Automated recommendations should remain subject to appropriate human oversight, especially where they affect access to services, safety or enforcement.

10. Illustrative Case: Connected Flood-Management District

Background

Consider an illustrative medium-sized city developing a flood-management district around a rapidly urbanizing river corridor. The district contains roads, culverts, detention basins, pumping stations, public buildings and a construction zone.

Problem

Flood warnings are delayed because rainfall, water-level and pump data are held by separate departments. Field staff inspect equipment manually, and a communications outage can prevent the control centre from seeing local conditions. The city also lacks a consistent geospatial asset register.

Analysis

The project team identifies four service requirements:

1. Local pumps must continue safe operation during loss of external communications.
2. The control centre needs near-real-time status and alarms.
3. Historical data are needed for planning and maintenance.
4. Data must be shared among drainage, roads, emergency management and construction teams.

A hazard and consequence assessment classifies pump control as more critical than public dashboard display. This leads to different availability, cybersecurity and recovery requirements for each function.

Approach and solution

Water-level, rainfall, pump-current and gate-position sensors are installed with documented asset IDs and calibration records. Local controllers perform threshold-based protective actions. A fibre connection links major pump stations where available; cellular connectivity provides a diverse backup path. Low-power wireless devices are used for selected remote environmental measurements.

An edge gateway filters duplicate readings, checks plausible ranges and sends alarms immediately. The cloud platform stores time-series and spatial data, provides dashboards and supports long-term analysis. GIS links each sensor and pump to the drainage network, parcel boundaries and emergency access routes. APIs allow authorized departments to retrieve common datasets.

The system includes local backup power, manual override, network segmentation, certificate-based device identity and tested recovery procedures. Raw camera data are not continuously transmitted; only event information needed for flood operations is shared with the central platform.

Outcome

The arrangement reduces dependence on a single communications path, improves shared situational awareness and creates a maintainable asset register. It does not eliminate flooding or guarantee perfect prediction. Its value depends on continuing calibration, inspections, software maintenance, staff training and periodic exercises.

Learning points

The case demonstrates that smart infrastructure is a combination of physical design, sensing, communications, computing, governance and human procedures. Edge control supports resilience, GIS supports coordination, and open interfaces support institutional interoperability. Most importantly, service requirements should determine the architecture.

11. Implementation and Professional Practice

A construction or infrastructure team should address the following sequence:

1. Define the service outcome and failure consequences.
2. Identify assets, stakeholders, data owners and operational users.
3. Specify measurement requirements, including accuracy, sampling and calibration.
4. Select communications using coverage, latency, power and lifecycle criteria.
5. Allocate functions among device, edge, regional and cloud layers.
6. Establish geospatial references and persistent asset identifiers.
7. Define APIs, data models, metadata and interoperability requirements.
8. Design cybersecurity, privacy, backup and recovery measures.
9. Coordinate physical provisions: ducts, cabinets, power, cooling, access and protection.
10. Test commissioning, failure modes, data quality and user workflows.
11. Plan operation, maintenance, upgrades and end-of-life replacement.

Procurement documents should avoid vague statements such as “smart-ready.” They should specify measurable requirements, interfaces, testing procedures, ownership of data, software support periods and responsibilities for cybersecurity. Total cost of ownership includes installation, connectivity subscriptions, calibration, batteries, licenses, energy, staffing, upgrades and disposal.

Challenges and Limitations

Smart-city infrastructure faces several persistent limitations. Sensors can drift, fail or be vandalized. Wireless coverage can change as buildings and vegetation change. Cloud services may introduce dependency on vendors and communications. Digital models can become obsolete if construction changes are not recorded. Data integration is difficult where agencies use different asset names, coordinate systems and contractual arrangements.

There is also a risk of technological determinism—the belief that adding technology automatically improves urban outcomes. A poorly designed automated process may increase inequity, surveillance or operational complexity. Digital infrastructure consumes energy and requires materials, replacement equipment and electronic-waste management. Decisions should therefore consider sustainability across the life cycle, including embodied impacts, energy demand, repairability and reuse.

Contemporary Developments

Current development is moving toward AI-assisted anomaly detection, real-time digital twins, private 5G networks, open urban-data platforms, low-power satellite connectivity and more capable edge devices. AI can identify unusual energy consumption, predict equipment failure or classify traffic conditions, but its outputs depend on data quality and model validity. AI systems should be monitored for false alarms, bias, drift and inappropriate automation.

Open-source software and open standards can reduce dependency and encourage innovation, but they do not remove the need for professional support, security updates or governance. Sustainable smart-city design increasingly emphasizes interoperability, modularity, low-carbon operation, transparent procurement and the ability to repair or replace components without discarding the entire system.

Chapter Summary

Smart cities depend on coordinated digital and physical infrastructure. IoT sensors measure urban conditions, while actuators influence physical processes. Communication networks must be selected according to coverage, capacity, latency, power, reliability and lifecycle requirements. Fibre, Wi-Fi, cellular, 5G and low-power networks have complementary roles.

Cloud computing provides centralized scalability and analytics; edge computing supports low-latency, privacy-preserving and resilient local operation. Geospatial infrastructure connects data to places, assets and networks, while digital twins combine models with current operational information. Data centers and urban platforms provide storage, processing, integration, APIs and governance capabilities.

Reliability requires attention to failure, repair, redundancy and common-cause risk. Scalability includes devices, data, users, operations and physical facilities. Interoperability requires technical, syntactic, semantic and organizational agreement. Cybersecurity, privacy, accountability and maintainability must be designed into the system. The central professional lesson is that technology should follow clearly defined urban services and risk-based requirements.

Key Terms

IoT: Network of physical objects capable of sensing, communicating, computing or acting.

Sensor: Device that measures a physical quantity and produces a signal or data value.

Actuator: Device that converts a command into physical action.

Edge computing: Processing performed near the source of data or point of action.

Cloud computing: On-demand provision of shared computing and storage resources.

Fog computing: Distributed intermediate computing layer between edge devices and centralized cloud systems.

5G: A family of cellular technologies supporting enhanced capacity, mobility and connected-device services.

Latency: Time delay between an event, its transmission and processing.

Bandwidth: Maximum data-transfer capacity of a communication channel.

Availability: Proportion of time that a service is operational and accessible as required.

Reliability: Probability that a system performs successfully for a specified period and condition.

Scalability: Ability to maintain acceptable service as demand increases.

Interoperability: Ability of systems to exchange and meaningfully use information.

GIS: Geographic information system for managing, analyzing and displaying location-based data.

Digital twin: Data-linked digital representation of a physical asset or system.

API: Defined interface through which software systems exchange functions or data.

LPWAN: Low-power wide-area network designed for long-range, low-data-rate communication.

Metadata: Information describing the meaning, origin, quality, format or status of data.

Network resilience: Capacity to withstand, adapt to and recover from communication disruption.

Cyber-physical system: System in which computational and physical processes interact.

Review Questions

Short Answer Questions

1. What is the difference between a sensor and an actuator?
2. Define edge computing and state one advantage it offers in a smart-city system.
3. Name three factors that influence the selection of an urban communication network.
4. What is meant by semantic interoperability?
5. Why are geospatial asset identifiers important in urban infrastructure management?

Long Answer Questions

1. Explain the layered architecture of digital and physical smart-city infrastructure, using an urban example.
2. Compare cloud computing, edge computing and fog computing in terms of latency, resilience, bandwidth and governance.
3. Discuss the role of 5G in smart cities and explain why it should not be treated as a universal replacement for other networks.
4. Explain how reliability, availability, redundancy and maintainability should influence infrastructure design.
5. Describe the functions of an urban data platform and the governance controls required for its responsible operation.

Analytical / Application Questions

1. A city plans to connect battery-powered air-quality sensors, mobile buses and pumping stations. Recommend a communication architecture and justify your choices using coverage, power, latency, reliability and cost criteria.
2. Design a high-level cloud-edge architecture for a connected construction site that uses cameras, equipment-monitoring sensors and worker-safety alerts. Identify which functions should remain local and which may be centralized.
3. Using the availability equation, compare two services: Service A has MTBF = 500 hours and MTTR = 5 hours; Service B has MTBF = 2,000 hours and MTTR = 40 hours. Calculate both operational availabilities and explain which service has the higher availability and why.

Multiple Choice Questions with Answers

Question 1

Which component converts a physical measurement into a data signal?

A. Actuator

B. Sensor

C. Router

D. Database

Correct Answer: B. Sensor

Question 2

What is a principal advantage of edge computing?

A. It always eliminates the need for cybersecurity

B. It guarantees unlimited storage

C. It can reduce latency and support local operation during connectivity loss

D. It replaces all physical infrastructure

Correct Answer: C. It can reduce latency and support local operation during connectivity loss

Question 3

Which technology is generally most suitable as a high-capacity fixed urban backbone?

A. Fibre optic

B. Bluetooth

C. LPWAN

D. Infrared remote control

Correct Answer: A. Fibre optic

Question 4

If MTBF is 990 hours and MTTR is 10 hours, what is the operational availability under the stated availability model?

A. 90.0%

B. 98.0%

C. 99.0%

D. 99.9%

Correct Answer: C. 99.0%

Question 5

Which statement best describes semantic interoperability?

A. Devices use the same electrical voltage

B. Systems understand exchanged data consistently

C. All systems are operated by one company

D. Every dataset is stored in a single server

Correct Answer: B. Systems understand exchanged data consistently

Question 6

What is the main purpose of a geographic information system in smart-city infrastructure?

A. To replace all network equipment

B. To manage and analyze data associated with location

C. To increase battery voltage

D. To encrypt every message automatically

Correct Answer: B. To manage and analyze data associated with location

Question 7

Which function should normally remain available locally in a safety-critical pump system?

A. A decorative dashboard theme

B. A threshold-based protective control

C. Long-term historical reporting

D. Public website advertising

Correct Answer: B. A threshold-based protective control

Question 8

What does scalability refer to in an urban data platform?

A. The ability to operate only without maintenance

B. The ability to maintain acceptable service as demand grows

C. The ability to use only wireless connections

D. The ability to avoid all data standards

Correct Answer: B. The ability to maintain acceptable service as demand grows

Question 9

Which practice best supports cybersecurity for connected urban devices?

A. Using one shared password for every device

B. Disabling all software updates

C. Using unique identities and least-privilege access

D. Publishing device credentials publicly

Correct Answer: C. Using unique identities and least-privilege access

Question 10

In a series system where every independent component must operate, how is system reliability calculated?

A. By adding component reliabilities

B. By multiplying component reliabilities

C. By subtracting the highest reliability from one

D. By averaging only the repair times

Correct Answer: B. By multiplying component reliabilities