AWS IoT Core architecture in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AWS IoT Core?

AWS IoT Core is a managed cloud service that lets connected devices easily and securely interact with cloud applications and other devices.

beginner

Name the main components of AWS IoT Core architecture.

The main components are: Device Gateway, Message Broker, Rules Engine, Device Shadows, and Registry.

intermediate

What role does the Device Gateway play in AWS IoT Core?

The Device Gateway securely receives messages from devices using MQTT, HTTP, or WebSocket protocols and routes them to the Message Broker.

intermediate

Explain the purpose of the Rules Engine in AWS IoT Core.

The Rules Engine evaluates inbound messages and routes them to other AWS services like Lambda, S3, or DynamoDB based on defined rules.

intermediate

What is a Device Shadow in AWS IoT Core?

A Device Shadow is a virtual representation of a device's state that allows applications to interact with devices even when they are offline.

Which protocol is NOT supported by AWS IoT Core for device communication?

A FTP

B HTTP

C WebSockets

D MQTT

AWS IoT Core supports MQTT, HTTP, and WebSockets but does not support FTP for device communication.

What component routes messages from devices to AWS services in AWS IoT Core?

A Device Gateway

B Message Broker

C Device Shadow

D Rules Engine

The Rules Engine routes messages to AWS services based on rules. The Message Broker routes messages between devices.

What does the Device Shadow allow you to do?

A Store device firmware

B Manage device certificates

C Represent device state virtually

D Encrypt device messages

Device Shadows provide a virtual representation of device state for applications to interact with devices even when offline.

Which AWS IoT Core component securely accepts device connections?

A Device Gateway

B Rules Engine

C Registry

D Message Broker

The Device Gateway securely accepts connections from devices using supported protocols.

What is the Registry used for in AWS IoT Core?

A Managing AWS user accounts

B Storing device metadata and identities

C Running device code

D Routing messages

The Registry stores information about devices such as metadata and identities.

Describe the flow of a message from a device to an AWS service in AWS IoT Core architecture.

Think about how the message moves step-by-step through the components.

Explain how AWS IoT Core supports device state management when devices are offline.

Focus on the virtual representation of device state.

Practice

1. What is the primary role of the message broker in AWS IoT Core architecture?

easy

A. To store device data permanently

B. To analyze data and generate reports

C. To register new devices automatically

D. To securely route messages between devices and AWS services

Solution

1. Step 1: Understand the message broker function

   The message broker acts as a middleman that routes messages securely between connected devices and AWS services.

2. Step 2: Differentiate from other components

   Storing data permanently is done by other AWS services, device registration is handled by the device registry, and data analysis is done by analytics services.

3. Final Answer:

   To securely route messages between devices and AWS services -> Option D

4. Quick Check:

   Message broker = Secure message routing [OK]

Hint: Message broker routes messages securely, not stores or analyzes [OK]

Common Mistakes:

• Confusing message broker with data storage
• Thinking message broker registers devices
• Assuming message broker analyzes data

2. Which AWS IoT Core component is responsible for managing device identities and metadata?

easy

A. Device registry

B. Shadow service

C. Message broker

D. Rules engine

Solution

1. Step 1: Identify the device registry role

   The device registry stores information about device identities and metadata, managing device details securely.

2. Step 2: Contrast with other components

   The rules engine processes messages, the message broker routes messages, and the shadow service manages device state.

3. Final Answer:

   Device registry -> Option A

4. Quick Check:

   Device registry = Device identity management [OK]

Hint: Device registry manages device info, not message routing [OK]

Common Mistakes:

• Mixing device registry with rules engine
• Confusing shadow service with device registry
• Assuming message broker manages device metadata

3. Given the following AWS IoT Core flow: A device publishes data to a topic, the rules engine triggers an action to store data in Amazon S3. What is the expected outcome?

medium

A. Data is stored in Amazon S3 bucket as per the rule action

B. Data is lost because rules engine cannot store data

C. Device registry updates device metadata with data

D. Message broker blocks data from reaching S3

Solution

1. Step 1: Understand the data flow in AWS IoT Core

   The device publishes data to a topic; the message broker routes it to the rules engine.

2. Step 2: Recognize the rules engine action

   The rules engine triggers actions such as storing data in Amazon S3 based on defined rules.

3. Final Answer:

   Data is stored in Amazon S3 bucket as per the rule action -> Option A

4. Quick Check:

   Rules engine triggers storage = Data saved [OK]

Hint: Rules engine triggers actions like storing data [OK]

Common Mistakes:

• Assuming rules engine cannot store data
• Confusing device registry with data storage
• Thinking message broker blocks data

4. A developer configures an AWS IoT rule to send device data to an Amazon DynamoDB table, but no data appears in the table. What is the most likely cause?

medium

A. The rule's SQL statement syntax is incorrect

B. The DynamoDB table does not exist or lacks write permissions

C. The device is not connected to AWS IoT Core

D. The message broker is down

Solution

1. Step 1: Check AWS IoT rule and permissions

   If the rule is configured but data is missing, the DynamoDB table might not exist or the rule lacks permission to write to it.

2. Step 2: Eliminate other causes

   If the device is connected and the SQL syntax is correct, and the message broker is operational, permissions or table existence is the likely issue.

3. Final Answer:

   The DynamoDB table does not exist or lacks write permissions -> Option B

4. Quick Check:

   DynamoDB permissions missing = No data stored [OK]

Hint: Check DynamoDB permissions and existence first [OK]

Common Mistakes:

• Assuming device is disconnected without checking
• Ignoring SQL syntax errors
• Blaming message broker without evidence

5. You want to design an AWS IoT Core solution where devices send telemetry data, and you need to keep device states synchronized even when devices go offline. Which AWS IoT Core feature should you use to achieve this?

hard

A. Device registry

B. Message broker

C. Device shadow service

D. Rules engine

Solution

1. Step 1: Identify the need for state synchronization

   Keeping device states synchronized, especially when devices are offline, requires a persistent state representation.

2. Step 2: Match feature to requirement

   The device shadow service maintains a virtual representation of device state, allowing updates and synchronization even if the device is offline.

3. Step 3: Exclude other components

   The device registry manages identities, the message broker routes messages, and the rules engine processes data but none maintain device state persistently.

4. Final Answer:

   Device shadow service -> Option C

5. Quick Check:

   Device shadow = Offline state sync [OK]

Hint: Use device shadow to sync states offline [OK]

Common Mistakes:

• Confusing device registry with state management
• Thinking message broker stores device state
• Assuming rules engine handles state sync