Knowledge Check: IoT Domain Requirements
Knowledge Check: IoT Domain Requirements
animation
applications
requirements
KC_DomReq1 = {
const question = makeInlineKnowledgeCheck({
id: "domreq_latency_selection",
question: "A startup is building an IoT system for autonomous drone delivery in urban areas. The drones must detect and avoid obstacles in real-time while navigating at 40 km/h. Which latency requirement and processing architecture is MOST appropriate?",
options: [
"Less than 1 second latency with cloud-based processing -- urban areas have good cellular coverage for fast cloud round-trips",
"Less than 10 milliseconds latency with on-device edge computing -- obstacle avoidance at speed requires immediate local processing",
"Less than 1 minute latency with LPWAN connectivity -- drones move slowly enough that delayed responses are acceptable",
"Less than 50 milliseconds latency with a nearby fog computing node -- the drone can relay processing to ground stations"
],
correctIndex: 1,
difficulty: "intermediate",
feedback: {
correct: "Correct! At 40 km/h, the drone travels about 11 meters per second. A 10ms response time means the drone moves only 11 cm before reacting -- essential for obstacle avoidance. Cloud processing adds 50-200ms of network latency (0.5-2.2 meters of travel), which is too slow for collision avoidance. Edge computing on the drone itself is the only viable approach for safety-critical real-time decisions.",
incorrect: "Not quite. At 40 km/h (11 m/s), the drone travels 11 cm in 10ms but over 1 meter in 100ms. Obstacle avoidance requires sub-10ms response, which only on-device edge computing can guarantee. Cloud processing adds 50-200ms network latency. Fog nodes add variable latency depending on distance. LPWAN latency (seconds) would be catastrophic. Safety-critical, real-time applications always require local edge processing."
}
});
return ikcModule.createMultipleChoiceWidget(question);
}KC_DomReq2 = {
const question = makeInlineKnowledgeCheck({
id: "domreq_power_technology",
question: "A vineyard needs to deploy 500 soil moisture sensors across 200 hectares of remote farmland with no electrical infrastructure. Sensors report every 15 minutes. Which technology and power combination will achieve the LOWEST total cost of ownership over 5 years?",
options: [
"Wi-Fi sensors with solar panels -- Wi-Fi provides reliable data delivery and solar ensures unlimited power",
"NB-IoT sensors with rechargeable batteries -- cellular coverage reaches rural areas and batteries can be swapped annually",
"LoRaWAN sensors with long-life batteries (10-year) and 3-5 LoRaWAN gateways with solar power",
"Zigbee mesh sensors with mains power run via buried cables -- mesh networking provides excellent coverage"
],
correctIndex: 2,
difficulty: "intermediate",
feedback: {
correct: "Correct! LoRaWAN is ideal for this scenario: (1) Long range (2-15 km) means 3-5 gateways cover 200 hectares, (2) ultra-low power consumption with 15-minute reporting enables 10-year battery life, (3) sensor cost is $30-50 each, (4) no per-device connectivity fees. Total 5-year cost: ~$25K sensors + $5K gateways + $0 connectivity = ~$30K. Wi-Fi would need 200+ access points ($100K+). NB-IoT adds $2-5/month per device ($60K-150K in connectivity alone). Buried cables for 200 hectares would cost $500K+.",
incorrect: "Consider the full cost picture across 5 years for 500 sensors over 200 hectares. Wi-Fi range (50-100m) would need 200+ APs plus power infrastructure. NB-IoT cellular fees add $2-5/month per device ($60K-150K over 5 years). Zigbee mesh range (10-100m) would need thousands of relay nodes. LoRaWAN's combination of 2-15 km range (needing only 3-5 gateways), 10-year battery life, and zero per-device connectivity fees makes it the clear winner for large-scale agricultural deployments."
}
});
return ikcModule.createMultipleChoiceWidget(question);
}KC_DomReq3 = {
const question = makeInlineKnowledgeCheck({
id: "domreq_regulation_impact",
question: "A company that makes consumer fitness trackers ($150 retail, 12-month development cycle) wants to pivot to medical-grade patient monitoring wearables. Which statement BEST describes the impact on their business model?",
options: [
"Minimal impact -- the same hardware can be repackaged with a medical label and sold at a higher price point",
"Development timeline extends to 18-36 months, costs increase 200-500%, retail price rises to $500-2,000, but the addressable market and margins are significantly higher",
"The only difference is adding HIPAA compliance to data handling -- the device hardware and software remain essentially the same",
"The regulatory burden makes this pivot economically unviable for any company that is not already in the medical device industry"
],
correctIndex: 1,
difficulty: "advanced",
feedback: {
correct: "Correct! The pivot from consumer to medical-grade requires: the FDA pathway for the intended use, clinical data if required, HIPAA safeguards if the deployment is covered, performance evidence appropriate to the clinical claim, and product liability insurance. [source](https://www.fda.gov/training-and-continuing-education/cdrh-learn/510k-program-transcript) This can increase development cost and time, depending on the medical claim and regulatory pathway. However, the medical device market commands $500-2,000 retail prices with higher margins, insurance reimbursement, and stronger customer retention. Many successful companies (like Apple with ECG features) have made this transition.",
incorrect: "The transition from consumer wearable to medical device involves far more than just data compliance. Some Class II devices need a 510(k), but clinical testing is most often not required. [source](https://www.fda.gov/training-and-continuing-education/cdrh-learn/510k-program-transcript) Hardware must meet medical-grade accuracy standards (+/-0.1C temperature, +/-2 bpm heart rate). If HIPAA applies, the Security Rule requires risk-based safeguards; encryption is an addressable specification, and audit controls are required. Product liability exposure changes dramatically. However, this pivot IS economically viable -- a medically validated product may support a different price and market, but the business case must be tested. The key is budgeting for the product-specific validation, regulatory pathway, and operating costs."
}
});
return ikcModule.createMultipleChoiceWidget(question);
}KC_DomReq4 = {
const question = makeInlineKnowledgeCheck({
id: "domreq_data_volume_architecture",
question: "A manufacturing plant has 500 vibration sensors sampling at 100 Hz (400 bytes/sec per sensor). Raw data totals 17 GB/day. Edge processing can reduce this to 170 MB/day by sending only anomalies. What is the PRIMARY reason to implement edge processing in this scenario?",
options: [
"Edge processing improves sensor accuracy by filtering noise before data reaches the cloud",
"Edge processing reduces cloud storage and bandwidth costs by approximately 100x ($620/year vs $6/year), making the system economically viable at scale",
"Edge processing is required because cloud platforms cannot handle 17 GB/day of data",
"Edge processing eliminates the need for cloud infrastructure entirely, reducing architectural complexity"
],
correctIndex: 1,
difficulty: "intermediate",
feedback: {
correct: "Correct! The primary driver is economics. Cloud platforms can technically handle 17 GB/day, but the costs are prohibitive at scale: $620/year in cloud costs vs $6/year with edge processing -- a 100x reduction. For a plant with multiple production lines, this difference scales to tens of thousands of dollars annually. Edge processing also reduces bandwidth requirements (from 200 KB/sec to 2 KB/sec), enabling less expensive network infrastructure. While edge processing can also improve latency for real-time alerts, the economic argument is what makes the business case.",
incorrect: "Think about this from a business perspective. Cloud platforms absolutely can handle 17 GB/day -- major cloud providers handle petabytes daily. Edge processing doesn't eliminate cloud needs; you still need cloud for historical analysis, dashboards, and cross-plant comparisons. The primary driver is economics: sending 17 GB/day to the cloud costs ~$620/year per production line, while edge-processed 170 MB/day costs only ~$6/year -- a 100x reduction that makes predictive maintenance economically viable across hundreds of sensors."
}
});
return ikcModule.createMultipleChoiceWidget(question);
}KC_DomReq5 = {
const question = makeInlineKnowledgeCheck({
id: "domreq_scale_architecture",
question: "A university campus is deploying IoT sensors for energy management across 30 buildings with approximately 2,000 total sensor points (temperature, occupancy, lighting, HVAC). Which deployment scale category does this fall into, and what is the MOST appropriate network architecture?",
options: [
"Home scale -- use consumer Wi-Fi routers in each building with a cloud dashboard",
"Building scale -- deploy a single building management system with wired sensors in the main building only",
"Campus scale -- dedicated network infrastructure with LoRaWAN gateways or enterprise Wi-Fi, centralized gateway management, and a building management platform",
"City scale -- deploy NB-IoT cellular sensors to avoid campus network infrastructure costs"
],
correctIndex: 2,
difficulty: "intermediate",
feedback: {
correct: "Correct! With 2,000 sensors across 30 buildings, this is firmly in the campus scale (500-5,000 devices). Campus deployments need: dedicated network infrastructure (enterprise Wi-Fi or LoRaWAN gateways covering all buildings), centralized management for gateway/sensor fleet, professional installation, and a building management platform for cross-building analytics. Consumer Wi-Fi would lack the management capabilities. A single building system wouldn't cover 30 buildings. NB-IoT would add unnecessary per-device cellular costs when campus infrastructure can be deployed once.",
incorrect: "Consider the scale: 2,000 sensors across 30 buildings. This maps to the campus tier (500-5,000 devices). Home-scale solutions (consumer Wi-Fi) lack fleet management for 2,000 devices across 30 locations. Building-scale approaches only cover one building. City-scale NB-IoT adds per-device cellular fees ($2-5/month x 2,000 = $4K-10K/month) when the university can deploy its own LoRaWAN gateways or use existing enterprise Wi-Fi infrastructure for a one-time cost. Campus scale requires dedicated but self-managed network infrastructure."
}
});
return ikcModule.createMultipleChoiceWidget(question);
}