KPI alignment: Key Performance Indicators (KPIs) define success metrics for the wireless IoT solution (e.g., uptime, device responsiveness, data accuracy). Continuous monitoring tracks performance against these KPIs.
Meeting Business Needs: Monitoring ensures the solution delivers the intended value. Are response times fast enough? Are business processes supported effectively?
Proactive maintenance: Monitoring can reveal performance issues before they become critical failures, allowing for proactive fixes.
Optimization: Monitoring data over time helps identify areas for fine-tuning the solution to further align with business requirements.
References
Wireless IoT monitoring tools: Vendor documentation or articles on specific tools and the KPIs they can track.
ITIL (Information Technology Infrastructure Library): Frameworks emphasizing monitoring and continuous improvement.

Smart City Focus: Smart city initiatives mainly address infrastructure, environmental monitoring, and optimization of public services.
Ride-sharing Context: While self-driving technology could contribute to future smart city transportation, it's primarily a private-sector innovation, not a core municipal service like the other options.
Typical Smart City Applications:
Wi-Fi: Provides public internet access, enabling data collection
Pollution Monitoring: Tracks air/water quality for environmental management.
Demand-based Tolling: Adjusts pricing for traffic management.
References:
Smart City Examples: Case studies showcasing common application areas (infrastructure, environment, utilities).
Autonomous Vehicles and Smart Cities: Discussions of the potential interplay but emphasize the still-developing nature of self-driving tech.

IEEE 802.15.4: The IEEE 802.15.4 standard is a fundamental specification for low-rate wireless personal area networks (LR-WPANs). It serves as the basis for many wireless IoT protocols.
IEEE's Role: The Institute of Electrical and Electronics Engineers (IEEE) is the organization responsible for creating, maintaining, and publishing the 802.15.4 standard.
References
IEEE 802.15.4 Standard: https://standards.ieee.org/standard/802_15_4-2020.html IEEE Website: https://www.ieee.org/

SSL/TLS Secures Web Traffic: HTTPS builds upon HTTP, adding the encryption provided by Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS).
Other Protocols Have Different Purposes:
IPSec: Secures IP traffic at a network level, can be used alongside TLS.
SNMPv3: Management protocol, offers security features, but not the primary mechanism in HTTPS.
SSH: Secure remote shell, unrelated to web data encryption.
References:
TLS (and SSL): References of their role in HTTPS and how they provide encryption for web communication.
HTTPS Overview: Materials showing how TLS fits into the overall HTTPS architecture.

Bottom-Up Troubleshooting: The OSI model provides a structured diagnostic approach. Starting at Layer 1 ensures basic physical connectivity issues are ruled out first.
MQTT Relies on IP: MQTT operates at a higher layer of the OSI model, relying on TCP/IP (Layers 4 and 3) for communication. Problems at the physical layer will disrupt everything built upon it.
Checking the Fundamentals: Before investigating complex application issues (MQTT), verify cables, link lights, Wi-Fi signal strength, etc.
References:
OSI Model: Descriptions of the seven layers, emphasizing the foundation provided by Layer 1 (Physical).
Network Troubleshooting Guides: Resources that outline common Layer 1 problems and their symptoms.