Question 250
Standalone smart meters maintain authenticated outbound sessions to a cloud analytics endpoint without a nearby local hub. Which IoT ecosystem component or communication pattern is being described?
- Zigbee mesh connectivity
- Device-to-cloud telemetry
- CoAP constrained-device exchange
- MQTT publish-subscribe messaging
- Edge gateway mediation
Explanation
Correct Answer
B:Device-to-cloud models send telemetry directly to a hosted platform. Identity, encryption and revocation must scale to the device fleet.
Incorrect Answers
A:Zigbee supports low-power mesh networking for compatible devices; that is relevant to low-power wireless mesh forwarding but does not directly account for direct IoT endpoint-to-cloud communication.
C:CoAP is designed for constrained environments and supports lightweight resource interaction, often over UDP; that is relevant to lightweight UDP resource requests but does not directly account for direct IoT endpoint-to-cloud communication.
D:MQTT is a lightweight publish-subscribe protocol commonly used with constrained devices when analysts encounter topic-based sensor messaging broker; this question instead describes direct IoT endpoint-to-cloud communication.
E:An IoT gateway bridges protocols and may enforce authentication, filtering and telemetry between constrained devices and enterprise systems; it handles intermediary between field devices and enterprise, while the decisive evidence in the question is direct IoT endpoint-to-cloud communication.
Question 251
A vendor ships every network camera with the same administrative password, allowing one leak to compromise the entire fleet. Which IoT identity or provisioning safeguard is the best response?
- Secure device onboarding
- Mutual TLS device authentication
- Unique per-device credentials
- Hardware root of trust
Explanation
Correct Answer
C:Per-device secrets prevent a single shared credential from granting access across all units. Secure enrollment and rotation remain necessary.
Incorrect Answers
A:Secure onboarding establishes device identity, intended controller and authorized policy before normal operations when analysts encounter trusted first-time IoT enrollment; this question instead describes avoidance of fleet-wide shared passwords.
B:Mutual TLS can verify both connection peers using certificates and trusted issuers; that is relevant to two-way certificate identity validation but does not directly account for avoidance of fleet-wide shared passwords.
D:Secure elements or similar hardware roots can isolate identity keys and anchor trust operations; it handles hardware-bound IoT key custody, while the decisive evidence in the question is avoidance of fleet-wide shared passwords.
Question 252
A monitoring service must authenticate each sensor cryptographically while sensors also validate the server they contact. Which IoT identity or provisioning safeguard is the best response?
- Unique per-device credentials
- Mutual TLS device authentication
- Secure device onboarding
- Credential revocation at decommissioning
Explanation
Correct Answer
B:Mutual TLS can verify both connection peers using certificates and trusted issuers. Secure storage of each private key is critical.
Incorrect Answers
A:Per-device secrets prevent a single shared credential from granting access across all units when the underlying evidence concerns avoidance of fleet-wide shared passwords rather than the stated two-way certificate identity validation.
C:Secure onboarding establishes device identity, intended controller and authorized policy before normal operations; its distinguishing scope is trusted first-time IoT enrollment, not the reported two-way certificate identity validation.
D:Revocation or expiration of device identities prevents retired hardware from rejoining trusted services when analysts encounter invalidation of retired device identities; this question instead describes two-way certificate identity validation.
Question 253
Technicians install replacement sensors but have no trusted way to bind each serial number to an approved site and owner. Which IoT identity or provisioning safeguard is the best response?
- Credential revocation at decommissioning
- Mutual TLS device authentication
- Unique per-device credentials
- Secure device onboarding
Explanation
Correct Answer
D:Secure onboarding establishes device identity, intended controller and authorized policy before normal operations. It prevents accidental or hostile enrollment.
Incorrect Answers
A:Revocation or expiration of device identities prevents retired hardware from rejoining trusted services for the specific concern of invalidation of retired device identities, not the requirement involving trusted first-time IoT enrollment.
B:Mutual TLS can verify both connection peers using certificates and trusted issuers; it handles two-way certificate identity validation, while the decisive evidence in the question is trusted first-time IoT enrollment.
C:Per-device secrets prevent a single shared credential from granting access across all units; that is relevant to avoidance of fleet-wide shared passwords but does not directly account for trusted first-time IoT enrollment.
Question 254
Smart gateways must protect device signing secrets against extraction even if application software is compromised. Which IoT identity or provisioning safeguard is the best response?
- Unique per-device credentials
- Credential revocation at decommissioning
- Hardware root of trust
- Mutual TLS device authentication
Explanation
Correct Answer
C:Secure elements or similar hardware roots can isolate identity keys and anchor trust operations. Full system protection still depends on firmware design.
Incorrect Answers
A:Per-device secrets prevent a single shared credential from granting access across all units for the specific concern of avoidance of fleet-wide shared passwords, not the requirement involving hardware-bound IoT key custody.
B:Revocation or expiration of device identities prevents retired hardware from rejoining trusted services when analysts encounter invalidation of retired device identities; this question instead describes hardware-bound IoT key custody.
D:Mutual TLS can verify both connection peers using certificates and trusted issuers for situations characterized by two-way certificate identity validation; the case points instead to hardware-bound IoT key custody.
Question 255
Disposed sensors continue to authenticate to the telemetry broker because their certificates were never invalidated. Which IoT identity or provisioning safeguard is the best response?
- Hardware root of trust
- Unique per-device credentials
- Mutual TLS device authentication
- Secure device onboarding
- Credential revocation at decommissioning
Explanation
Correct Answer
E:Revocation or expiration of device identities prevents retired hardware from rejoining trusted services. Inventory must link credentials to physical assets.
Incorrect Answers
A:Secure elements or similar hardware roots can isolate identity keys and anchor trust operations in a setting defined by hardware-bound IoT key custody; the observed issue is invalidation of retired device identities.
B:Per-device secrets prevent a single shared credential from granting access across all units when analysts encounter avoidance of fleet-wide shared passwords; this question instead describes invalidation of retired device identities.
C:Mutual TLS can verify both connection peers using certificates and trusted issuers for situations characterized by two-way certificate identity validation; the case points instead to invalidation of retired device identities.
D:Secure onboarding establishes device identity, intended controller and authorized policy before normal operations; the operational difference is trusted first-time IoT enrollment versus the scenario's invalidation of retired device identities.
Question 256
A smart lock should reject an unauthorized update file even when the payload arrives through a trusted management connection. Which IoT firmware protection is most appropriate?
- Firmware bill of materials
- Signed firmware verification
- Anti-rollback protection
- Secure boot
Explanation
Correct Answer
B:Signature verification checks firmware provenance and integrity against approved trust anchors before installation. Trusted signing-key custody is crucial.
Incorrect Answers
A:A firmware SBOM enumerates software components and versions for exposure tracking; the operational difference is visibility of embedded firmware dependencies versus the scenario's checking authenticity of firmware images.
C:Anti-rollback controls reject versions older than an approved security floor, reducing attacks through valid yet vulnerable historical builds; the operational difference is blocking vulnerable firmware downgrades versus the scenario's checking authenticity of firmware images.
D:Secure boot chains verification through startup components, establishing a trusted execution foundation when keys and hardware are protected; this characterizes authentication of code before execution, whereas the reported condition is checking authenticity of firmware images.
Question 257
A device accepts signed but obsolete firmware containing a publicly known exploitable vulnerability after a downgrade attempt. Which IoT firmware protection is most appropriate?
- Secure boot
- Firmware bill of materials
- Anti-rollback protection
- Over-the-air update staging
Explanation
Correct Answer
C:Anti-rollback controls reject versions older than an approved security floor, reducing attacks through valid yet vulnerable historical builds.
Incorrect Answers
A:Secure boot chains verification through startup components, establishing a trusted execution foundation when keys and hardware are protected; its distinguishing scope is authentication of code before execution, not the reported blocking vulnerable firmware downgrades.
B:A firmware SBOM enumerates software components and versions for exposure tracking; that is relevant to visibility of embedded firmware dependencies but does not directly account for blocking vulnerable firmware downgrades.
D:Staged OTA deployment validates compatibility and health before expanding rollout in a setting defined by phased remote firmware delivery; the observed issue is blocking vulnerable firmware downgrades.
Question 258
A factory gateway must refuse to start if its bootloader or operating image has been modified without an authorized signature. Which IoT firmware protection is most appropriate?
- Over-the-air update staging
- Secure boot
- Anti-rollback protection
- Firmware bill of materials
Explanation
Correct Answer
B:Secure boot chains verification through startup components, establishing a trusted execution foundation when keys and hardware are protected.
Incorrect Answers
A:Staged OTA deployment validates compatibility and health before expanding rollout when analysts encounter phased remote firmware delivery; this question instead describes authentication of code before execution.
C:Anti-rollback controls reject versions older than an approved security floor, reducing attacks through valid yet vulnerable historical builds; that is relevant to blocking vulnerable firmware downgrades but does not directly account for authentication of code before execution.
D:A firmware SBOM enumerates software components and versions for exposure tracking in a setting defined by visibility of embedded firmware dependencies; the observed issue is authentication of code before execution.
Question 259
A faulty firmware release could interrupt thousands of remote sensors, so the vendor wants a small pilot before fleetwide upgrade. Which IoT firmware protection is most appropriate?
- Secure boot
- Over-the-air update staging
- Firmware bill of materials
- Signed firmware verification
Explanation
Correct Answer
B:Staged OTA deployment validates compatibility and health before expanding rollout. Rollback planning and monitoring are vital for remote devices.
Incorrect Answers
A:Secure boot chains verification through startup components, establishing a trusted execution foundation when keys and hardware are protected; this characterizes authentication of code before execution, whereas the reported condition is phased remote firmware delivery.
C:A firmware SBOM enumerates software components and versions for exposure tracking in a setting defined by visibility of embedded firmware dependencies; the observed issue is phased remote firmware delivery.
D:Signature verification checks firmware provenance and integrity against approved trust anchors before installation; this characterizes checking authenticity of firmware images, whereas the reported condition is phased remote firmware delivery.
Question 260
Security teams cannot determine which third-party libraries exist inside a smart camera's firmware image during a new vulnerability disclosure. Which IoT firmware protection is most appropriate?
- Anti-rollback protection
- Secure boot
- Signed firmware verification
- Firmware bill of materials
- Over-the-air update staging
Explanation
Correct Answer
D:A firmware SBOM enumerates software components and versions for exposure tracking. It needs maintenance across revisions.
Incorrect Answers
A:Anti-rollback controls reject versions older than an approved security floor, reducing attacks through valid yet vulnerable historical builds; that is relevant to blocking vulnerable firmware downgrades but does not directly account for visibility of embedded firmware dependencies.
B:Secure boot chains verification through startup components, establishing a trusted execution foundation when keys and hardware are protected; the operational difference is authentication of code before execution versus the scenario's visibility of embedded firmware dependencies.
C:Signature verification checks firmware provenance and integrity against approved trust anchors before installation; this characterizes checking authenticity of firmware images, whereas the reported condition is visibility of embedded firmware dependencies.
E:Staged OTA deployment validates compatibility and health before expanding rollout when the underlying evidence concerns phased remote firmware delivery rather than the stated visibility of embedded firmware dependencies.