Richfield BSc IT revision

Big Data & IoT 600 Study Hub

A dark, readable one-page guide covering the high-yield focus areas and the full module content from the 2026 Big Data & IoT 600 learner guide.

Definitions Benefits Exam traps Security risks Architecture

Exam Focus Areas

These cards are built from the learner guide outcomes, review questions, and repeated chapter themes. Start here when revising under time pressure.

Exam Overview

The guide is organized around five connected capabilities: explaining big data, designing IoT systems, selecting IoT technologies and standards, securing storage, and using analytics for strategy.

Focus What to know Typical answer pattern
Big Data foundations Definition, 5Vs, sources, tools, analysis techniques, cleaning, normalization, transformation. Define the term, classify the data/problem, then recommend a tool or preprocessing step.
IoT systems Devices, sensors, gateways, edge/cloud processing, layered architecture, applications, security concerns. Describe the data flow from sensing to action and identify the security weakness.
Standards and protocols MQTT, CoAP, HTTP, DDS, 6LoWPAN, BLE, LoRaWAN, NB-IoT, Zigbee, Wi-Fi, 5G, security and privacy standards. Match the protocol to power, range, latency, bandwidth, and reliability needs.
Storage and security HDFS, Hadoop, NoSQL, cloud storage, data lakes, replication, governance, encryption, IAM, monitoring. Explain why traditional storage is insufficient, then propose scalable and secure architecture.
Strategy and analytics Big data strategy, descriptive/diagnostic/predictive/prescriptive analytics, visualization, ethics, monitoring. Connect analytics outputs to business decisions, risks, KPIs, and continuous improvement.
Exam FocusDefinitions

Big Data Foundations and Preprocessing

Big Data means datasets too large, complex, fast, or varied for traditional tools. The guide frames it through the 5Vs: volume, variety, velocity, veracity, and value.

  • Sources include business transactions, social media, IoT devices, healthcare systems, scientific research, and government/public services.
  • Common tools include Hadoop, Spark, Kafka, MongoDB, Tableau, AWS, Flink, and Power BI.
  • Preprocessing prepares raw data through cleaning, normalization, and transformation.
Exam trap: do not treat cleaning, normalization, and transformation as the same step. Cleaning fixes errors, normalization standardizes scale or structure, and transformation reshapes data for analysis.
Exam FocusArchitecture

IoT Architecture, Applications, and Security

IoT connects physical objects, sensors, software, networks, and platforms so devices can collect, exchange, analyse, and act on data in real time.

  • The ecosystem includes devices/sensors, connectivity, processing, platforms, applications, and security frameworks.
  • The five-layer model moves from perception to network, middleware, application, and business layers.
  • Security challenges cluster around encryption, authentication, and privacy protection.
Security warning: default credentials, weak key management, and poor privacy controls are recurring IoT failure points.
Exam FocusProtocols

IoT Protocols, Technologies, and Standards

Chapter 3 asks you to compare technologies, communication protocols, data formats, and standards that make IoT systems interoperable and secure.

  • Use MQTT for lightweight publish/subscribe messaging where bandwidth and power are limited.
  • Use CoAP for constrained devices that need REST-like interactions over low overhead networks.
  • Use LoRaWAN or NB-IoT for long-range, low-power applications; use Wi-Fi or 5G where higher bandwidth or low latency matters.
Correct pattern: protocol choice should always mention the use case, power budget, range, bandwidth, latency, and security needs.
Exam FocusSecurity

Big Data Storage and Security

Big data storage must support scale, flexibility, fault tolerance, high throughput, distributed processing, and secure access to sensitive data.

  • Hadoop combines HDFS for distributed storage with MapReduce for distributed processing, plus YARN and Hadoop Common.
  • Storage options include distributed file systems, NoSQL databases, cloud storage, data lakes, and hybrid/multi-cloud architectures.
  • Security techniques include encryption, access control, masking, MFA, anomaly detection, segmentation, backup, audits, and monitoring.
Exam trap: scalability alone is not enough. A strong answer also explains fault tolerance, governance, regulatory compliance, and data integrity.
Exam FocusStrategy

Strategy Development and Big Data Analytics

Big Data supports strategic decisions by revealing patterns, forecasting changes, improving efficiency, and grounding decisions in evidence.

  • A strategy needs collection, integration, storage, processing, analytics, governance, security, talent, tools, scalability, and business alignment.
  • The four analytics types answer: what happened, why it happened, what could happen, and what should be done.
  • Ethical strategy requires privacy, transparency, fairness, ownership clarity, security, and limits on unintended data use.
Memory hook: descriptive = happened, diagnostic = why, predictive = next, prescriptive = action.

General Module Content

All chapter content is visible by default. Use the cards as a compact map of the learner guide, then return to the exam focus cards when testing yourself.

Chapter 1: Big Data Analysis and Extraction Techniques

This chapter introduces Big Data, its sources, analysis tools, analytics techniques, and the preprocessing steps needed before modelling or decision-making.

1.1 Big Data

Big Data describes extremely large datasets that are too voluminous, complex, or fast-moving for traditional data-processing tools to handle effectively. Managing it requires specialized technologies for storage, processing, analysis, and retrieval.

The guide links Big Data directly to efficient storage and analysis: organizations must manage volume, variety, velocity, and veracity so they can extract value.

1.2 Characteristics of Big Data: The Five Vs

V Meaning Revision cue
Volume Huge amounts of data, often growing into terabytes, petabytes, exabytes, or more. Storage scale and cloud/distributed systems.
Variety Different forms of data: structured, semi-structured, and unstructured text, images, audio, and video. Choose flexible tools such as NoSQL or data lakes.
Velocity The speed of data generation and the speed at which it must be analysed or acted on. Streaming, real-time analytics, Kafka, Flink.
Veracity The accuracy, reliability, uncertainty, and trustworthiness of data from multiple sources. Cleaning, validation, governance.
Value The usefulness gained from analysing data and turning it into knowledge or action. Analytics must support decisions.

Sources of Big Data

Sources include business transactions, social media interactions, IoT sensor streams, digital activity, healthcare records, scientific experiments, and government/public-service datasets.

1.3 Common Tools and Frameworks

Tool Primary purpose Best fit from the guide
Hadoop Distributed storage and batch processing using HDFS and MapReduce. Large structured, semi-structured, or unstructured datasets with fault tolerance.
Apache Spark In-memory big data analytics for batch, streaming, and machine learning workloads. Faster processing and mixed batch/stream use cases.
Apache Kafka Distributed event streaming and high-throughput real-time data flows. High-velocity data streams and durable event messaging.
MongoDB NoSQL document database for semi-structured and unstructured data. Flexible, schema-light data storage.
Tableau / Power BI Visualization dashboards, charts, and insight sharing. Communicating findings from large datasets.
AWS / Azure-style cloud platforms Cloud processing, storage, analytics, and scalable infrastructure. Elastic and cost-managed big data workflows.
Apache Flink Low-latency stream and batch processing. Event-driven and real-time applications.
Choosing a tool: match the tool to data type, processing need, scalability, and affordability.

1.4 Big Data Analysis Techniques

Descriptive analysis

Summarizes historical data to answer what happened, often through reports, dashboards, and infographics.

Predictive analytics

Uses historical data and machine learning models to forecast future events such as demand, defaults, or market trends.

Machine learning and deep learning

Allows systems to learn from data, improve over time, classify records, cluster groups, and model complex patterns.

Real-time analytics

Processes data as it is generated so decisions can happen immediately, such as fraud detection or IoT maintenance alerts.

Sentiment analysis

Uses natural language processing to classify text as positive, negative, or neutral.

1.5 Data Cleaning, Normalization, and Transformation

Step Purpose Examples
Cleaning Find and correct errors, inconsistencies, duplicates, missing values, and outliers. Imputation, duplicate removal, typo correction, date/number format standardization.
Normalization Standardize or scale data to make it easier to compare and process. Min-max scaling, z-score standardization, log transformation, label or one-hot encoding.
Transformation Convert raw data into formats suitable for analysis or model construction. Aggregation, encoding, wrangling, feature engineering, type conversion.
Case study route: for the RetailMax pipeline, mention each source, clean missing/duplicate records, normalize customer/product fields, transform JSON/CSV/MongoDB records into a unified customer view, then segment by purchase behavior, lifetime value, and preferences.
Back to Exam Focus Areas

Chapter 2: IoT Architectures and Applications

This chapter explains the IoT ecosystem, device-to-cloud data flow, layered architecture, security challenges, and major IoT application domains.

2.1 Core IoT Concepts and Principles

IoT is a network of physical objects, sensors, software, and technologies that communicate and share information online. It supports real-time data collection, sharing, analysis, automation, and better decisions.

Devices and sensors: collect environmental data or perform physical actions.
Connectivity: Wi-Fi, Bluetooth, Zigbee, Ethernet, 4G/5G, and other links.
Data processing: edge computing near the device or cloud computing in centralized systems.
Platforms: middleware for device management, data analysis, and application development.
Applications: user interfaces and dashboards for monitoring and control.
Security frameworks: encryption, authentication, and access control.

2.2 How IoT Works

IoT devices communicate over the internet or local networks. Data is captured by sensors, sent through an IoT gateway, processed locally at the edge or centrally in the cloud, and then used to trigger analysis, alerts, dashboards, or actuator commands.

Sense Devices capture data such as temperature, motion, location, or health metrics.
Connect Networks move data through gateways or directly to platforms.
Process Edge, fog, or cloud systems clean and analyse the stream.
Decide Applications detect patterns, predictions, or thresholds.
Act Users or actuators respond with alerts, controls, or automation.

2.3 Layer Architecture of IoT

Layer Role Example function
Perception Collects physical-world data using sensors and actuators. Temperature, moisture, sound, or intrusion detection.
Network Transfers data from perception to middleware using communication technologies. Wi-Fi, infrared, 3G, 4G, UTMS-style links.
Middleware Stores, processes, computes, and selects relevant information. Device lookup by name/address and decision logic.
Application Controls end-user operations and services. Alarms, smart agriculture, security systems, wearable apps.
Business Analyses service performance and presents value to users or managers. Graphs, flowcharts, optimization, and business decisions.

2.4 IoT Architectures and Building Blocks

The guide describes smart devices as objects with sensors and actuators that collect data and initiate physical action. IoT is enabled by tagging, sensing, thinking, and shrinking.

  • RFID tagging: identifies and tracks objects.
  • Sensing: gathers contextual or environmental data.
  • Thinking/smart technology: supports automation and intelligent decisions.
  • Nanotechnology/shrinking: makes components smaller for smoother integration.

System building blocks

Gateways connect devices to cloud systems, filter data, support protocol compatibility, and transmit commands. IoT data may enter a data lake in raw form, move into a warehouse for structured analysis, and feed machine-learning models or control applications.

2.5 Evaluating IoT Security Challenges

Area Challenge Resolution techniques
Encryption Resource-limited devices, complex end-to-end encryption, difficult key management. Low-power encryption such as ECC, PKI key management, transport-level encryption such as TLS.
Authentication Default credentials, huge device scale, device impersonation, limited support for advanced methods. Remove defaults, strong passwords, MFA where possible, secure boot, certificate-based authentication.
Privacy Sensitive behavioral, personal, and environmental data; compliance across regions. Privacy-by-design, transparency, opt-out controls, anonymisation, encryption, regular compliance checks.

2.6 IoT Applications

Smart homes

Thermostats, lighting, cameras, and locks improve energy use, convenience, and security.

Healthcare / IoMT

Wearables, smart pills, inhalers, and beds support remote monitoring and personalized care.

Industrial IoT

Sensors and connected machines enable predictive maintenance, smart factories, and supply-chain optimization.

Agriculture

Soil sensors, livestock monitoring, and autonomous drones improve yield and resource management.

Smart cities

Traffic systems, waste management, and street lighting improve city services and energy use.

Transport and logistics

Fleet management, connected cars, and cargo sensors improve safety and efficiency.

Retail

Smart shelves, beacons, and automated checkout improve inventory and customer experience.

Energy and environment

Smart grids, meters, pollution sensors, water quality systems, and wildlife tracking improve sustainability.

Back to Exam Focus Areas

Chapter 3: IoT Technologies and Standards

This chapter focuses on the technologies, protocols, and standards that allow IoT devices to sense, connect, process, secure, store, and exchange data.

3.1 IoT Technologies: Overview

Technology area Purpose Examples from the guide
Sensing and actuation Capture environmental data and perform physical action. Proximity sensors, environmental sensors, valves, robotic arms.
Connectivity Allow devices to communicate across short-range, long-range, and high-speed links. Bluetooth, Zigbee, LoRaWAN, NB-IoT, 5G.
Edge, fog, cloud Process data close to devices, between edge and cloud, or centrally in the cloud. Low-latency edge decisions, fog distribution, cloud analytics.
Storage and analytics Store raw or structured IoT data and extract insight. Data lakes, data warehouses, Hadoop, Spark, AI, machine learning.
Identification Track or identify objects securely. RFID and NFC.
Security and integration Secure communications and connect platforms/devices. TLS, DTLS, authentication, blockchain, middleware platforms, API gateways.
Power and nanotechnology Extend device life and enable miniaturized sensors. Energy harvesting, low-power chips, nanosensors.

3.2 IoT Communication Protocols

Protocol Type Best use Key point
MQTT Application Lightweight sensor messaging with publish/subscribe topics. QoS levels range from no guarantee to exactly-once delivery.
HTTP Application Web-style request/response communication. Often too heavy for battery-powered IoT.
CoAP Application Constrained networks and low-power devices. REST-like GET, POST, PUT, DELETE over lower overhead transport.
DDS Application High-demand, real-time systems without brokers. Devices share a Global Data Space.
AMQP Application Reliable messaging with delivery guarantees. More overhead than MQTT.
OPC UA Application / industrial Industrial interoperability. Transport-agnostic and vendor-neutral.
6LoWPAN Network IPv6 for low-power wireless personal-area networks. Useful with smart meters and environmental sensors.
BLE Network Short-range low-power wearables and medical monitors. Best for periodic communication.
LoRaWAN / NB-IoT Network Long-range low-power systems. Useful in agriculture, utilities, smart cities, and remote monitoring.
Zigbee / Wi-Fi / 5G Network Mesh smart-home networks, high-speed local networks, and ultra-low latency applications. Match choice to range, speed, latency, and power.

3.3 IoT Standards

Standards ensure interoperability, security, privacy, and reliable communication across varied devices and vendors.

  • Connectivity standards: IPv6, 6LoWPAN, IEEE 802.15.4, LoRaWAN, and NB-IoT.
  • Application-level standards: MQTT, CoAP, OneM2M, and OASIS-style integration frameworks.
  • Security standards: TLS/SSL, DTLS, AES, IEEE 802.1X, PKI, OAuth 2.0, IPsec, ETSI EN 303 645, IoTSF guidance.
  • Privacy and data protection: GDPR and ISO/IEC 27001.
  • Industrial IoT: OPC UA and ISA/IEC 62443 for secure industrial automation and control systems.

3.4 Data Standards in IoT

Data formats

JSON is lightweight and readable, XML is older and more verbose, and Protocol Buffers are compact for low-bandwidth serialization.

Security

TLS/SSL secures transmission, X.509 certificates authenticate devices, and OAuth2/OpenID Connect manage access.

Storage

SQL and NoSQL databases store structured and unstructured data; time-series databases handle timestamped IoT streams.

Interoperability

OneM2M, ODF, and AllJoyn help devices and applications work together across manufacturers.

Processing

Edge computing reduces latency, while Hadoop and Spark process high-volume IoT datasets.

Organizations

ISO/IEC, IEEE, IETF, and GSMA contribute standards for architecture, networking, protocols, and mobile IoT.

3.5 Practical Application of IoT Technologies and Standards

Practical IoT design combines technologies and standards to fit a domain. For example, a smart agriculture system might use soil sensors, LoRaWAN, edge computing, CoAP, OneM2M, and TLS. A hospital wearable may use BLE, MQTT, IEEE medical-device communication standards, and encrypted transmission.

Design-answer pattern: identify the environment, choose sensors, choose connectivity, decide edge/fog/cloud processing, choose protocol/standards, then explain security.
Back to Exam Focus Areas

Chapter 4: Big Data Storage and Security

This chapter covers storage fundamentals, Hadoop and HDFS, storage architectures, management techniques, and security frameworks for big data environments.

4.1 Fundamentals of Big Data Storage

Big data storage is infrastructure designed to store, manage, retrieve, sort, access, and process large datasets for analytics. It usually scales into terabyte or petabyte ranges and often relies on clusters of commodity servers attached to high-capacity storage.

The guide emphasizes flexibility, scalability, and parallel processing so analytic software can process data from diverse sources.

4.2-4.3 Apache Hadoop and Hadoop Architecture

Apache Hadoop is an open-source framework that distributes storage and processing across many cluster nodes. Its architecture is built around HDFS for storage and MapReduce for processing.

Component Role Why it matters
HDFS Splits files into blocks and stores them across cluster machines. Supports large-scale storage, replication, and fault tolerance.
NameNode Maintains the file-system namespace and block-to-DataNode mapping. Coordinates metadata and client access.
DataNode Stores blocks and serves read/write requests. Provides distributed data storage across worker machines.
MapReduce Splits processing into map and reduce phases. Processes large datasets in parallel.
YARN Manages and schedules cluster resources. Optimizes task execution across the cluster.

4.4 Big Data Storage Solutions

Distributed file systems

HDFS stores file blocks across multiple machines with replication for fault tolerance.

NoSQL databases

MongoDB, Cassandra, and Couchbase handle unstructured or semi-structured data with horizontal scalability.

Cloud storage

Cloud platforms offer on-demand scale, geographic redundancy, built-in security, and lower infrastructure burden.

Data lakes

Store raw structured, semi-structured, and unstructured data until it is needed for analysis.

4.5 Big Data Storage Architectures

Big data storage architectures are designed for enormous scale, variety, and speed. They rely on horizontal scalability, fault tolerance, distributed processing, and high throughput.

Architecture Core idea Advantage
Distributed file system Split data into blocks across nodes. Scalable, fault-tolerant batch storage.
NoSQL database Use document, column-family, key-value, or graph models. Flexible, fast, horizontally scalable storage.
Data lake Store raw data first, structure later. Flexible for analytics and machine learning.
Cloud-based storage Use elastic object storage and cloud analytics integration. Pay-as-you-go scale and remote access.
Hybrid / multi-cloud Combine on-premises and one or more cloud providers. Balance sensitivity, cost, performance, and geographic needs.

4.6 Data Management Techniques

  • Data storage solutions: distributed storage and cloud systems handle large scale and redundancy.
  • Data integration: ETL or ELT combines structured, semi-structured, and unstructured data from many sources.
  • Data governance: policies manage accuracy, access, compliance, and data lifecycle.
  • Data quality management: cleansing, validation, and enrichment keep analysis reliable.
  • Analytics and processing: machine learning, AI, real-time analytics, Spark, Hadoop, and data mining extract insight.
  • Scalability and flexibility: systems must grow as data volume grows.
  • Real-time processing: Kafka and Flink support continuous ingestion and event-driven decisions.

4.7 Big Data Security

Big data security protects privacy, prevents cyberattacks and theft, supports regulatory compliance, and preserves data integrity for decision-making.

Technique / framework Use
Encryption Protect data at rest and in transit.
Access control, IAM, RBAC, ABAC, MFA Restrict access to authorized users, roles, and attributes.
Data masking, tokenization, segmentation, sharding Limit exposure of sensitive information and reduce breach impact.
Anomaly detection, IDS, SIEM, monitoring, audits Detect unusual behavior, vulnerabilities, and policy violations.
Backup and recovery Restore operations after data loss or incidents.
NIST, CSA, ISO/IEC 27001, GDPR Provide structured approaches to cybersecurity, cloud security, ISMS, and privacy compliance.
Back to Exam Focus Areas

Chapter 5: Strategy Development and Big Data Analytics

This chapter connects Big Data to strategic decision-making, analytics types, visualization, business integration challenges, ethics, and continuous monitoring.

5.1 Role of Big Data in Strategic Decision-Making

Big Data helps organizations make evidence-based decisions by identifying patterns, forecasting trends, optimizing operations, understanding customers, and reducing reliance on intuition alone.

Strategy value: big data is useful when it improves anticipation, efficiency, personalization, and competitive decision-making.

5.2 Key Components of a Big Data Strategy

Collection and integration: gather data from internal, external, sensor, and platform sources.
Storage: choose scalable systems for large-volume retrieval and processing.
Processing: clean, structure, and enrich data with tools such as Hadoop or Spark.
Analytics and insights: use analytics, machine learning, and AI to find patterns.
Governance and security: manage privacy, compliance, access, and risk.
Talent and tools: rely on data scientists, analysts, engineers, cloud platforms, lakes, and visualization tools.
Scalability and flexibility: design for future data growth.
Business alignment: connect data work to organizational goals.

5.3 Data-Driven Strategy Formulation

A data-driven strategy starts with clear goals, gathers relevant data, analyses it for insights, develops a plan, implements it, and then measures and optimizes performance.

  1. Define measurable objectives.
  2. Identify and collect relevant data.
  3. Analyze and interpret the data.
  4. Build a plan from the insights.
  5. Implement the strategy and monitor progress.
  6. Measure, optimize, and repeat.
Retail example: the guide uses customer retention, online sales, segmentation, inventory optimization, delivery improvement, A/B testing, CRM, and analytics platforms to show how data becomes strategy.

5.4 Types of Big Data Analytics

Type Question answered Example use
Descriptive What happened? Summarize last year's sales and product performance.
Diagnostic Why did it happen? Find why sales dropped by checking complaints, market changes, or operational issues.
Predictive What could happen? Forecast demand, churn, risk, revenue, or market shifts.
Prescriptive What should we do? Recommend routes, schedules, promotions, pricing, or resource allocation.

5.5 Data Visualization for Strategy Communication

Visualization turns complex data into charts, graphs, dashboards, and visual stories so stakeholders can understand performance, track KPIs, spot trends, collaborate, and make faster decisions.

  • Line graphs can show customer sign-up growth.
  • Pie charts can show acquisition sources such as ads, referrals, or organic search.
  • Bar charts can compare campaign conversion rates.
  • Maps can show customer acquisition by region.

5.6 Challenges of Integrating Big Data with Business Strategy

Data quality

Incomplete, inconsistent, or outdated data can lead to weak decisions.

Data overload

Large volumes can hide relevant insight if filtering and prioritization are poor.

Legacy integration

Existing systems may not support big data scale and complexity.

Talent gaps

Data scientists, analysts, and engineers are needed to convert data into action.

Privacy and security

Sensitive customer data creates compliance and trust risks.

Cultural resistance

Teams may resist evidence-based decision-making if they rely on intuition.

Real-time processing

Fast-moving industries need infrastructure for up-to-date insights.

5.8 Monitor and Adjust Big Data Strategies

Big Data strategies should be monitored through goals, KPIs, real-time dashboards, processing performance, governance reviews, stakeholder feedback, infrastructure optimization, model evaluation, security checks, communication, and continuous improvement.

Answer pattern: set metrics, monitor systems and outcomes, review compliance and data quality, adjust technology or models, then communicate progress to stakeholders.
Back to Exam Focus Areas

Final Revision Tables

Use these for quick last-pass comparisons before answering scenario or discussion questions.

Architecture Quick Match

Need Likely choice
Raw mixed-format data for future analyticsData lake
Fast structured reportingData warehouse
Massive distributed file storageHDFS
Flexible semi-structured documentsMongoDB / NoSQL
Low-latency IoT decisionsEdge computing
Long-range low-power sensingLoRaWAN or NB-IoT

Security Quick Match

Risk Control
Data intercepted in transitTLS/SSL, DTLS, IPsec
Unauthorized user accessIAM, RBAC, MFA, strong passwords
Device impersonationCertificates, PKI, secure boot
Exposure of personal dataMasking, tokenization, anonymisation, privacy-by-design
Data alterationHashing, digital signatures, audits
Suspicious activityAnomaly detection, IDS, SIEM monitoring