Question 400
To stop modified update images from being installed on connected devices, what is the relevant defensive action?
- Secure manufacturing provisioning
- Unique device certificates
- OTA rollback protection
- Hardware root of trust
- Firmware signature verification
Explanation
Correct Answer
E:Authenticated update packages must pass trusted signature checks before being accepted; the requested outcome is precisely to stop modified update images from being installed on connected devices.
Incorrect Answers
A:Trusted enrollment injects unique credentials and records device identity before field deployment; that is useful when the task is to prevent cloning when devices initially receive certificates and keys, not the stated requirement to stop modified update images from being installed on connected devices.
B:Device-specific certificates permit targeted revocation when one endpoint is compromised; a team would select it to authenticate individual sensors without a shared fleet secret, which does not provide the particular result to stop modified update images from being installed on connected devices.
C:Anti-rollback metadata or monotonic counters reject signed but outdated images; its operational purpose is to prevent an attacker downgrading firmware to a known-vulnerable version, not to achieve the specific requirement to stop modified update images from being installed on connected devices.
D:Secure key storage separates private material from easily modified application firmware; applying it would serve protect device identities in a dedicated security element without directly satisfying the goal to stop modified update images from being installed on connected devices.
Question 401
To prevent an attacker downgrading firmware to a known-vulnerable version, which option most directly provides the capability?
- Secure manufacturing provisioning
- OTA rollback protection
- Firmware signature verification
- Credential rotation protocol
Explanation
Correct Answer
B:Anti-rollback metadata or monotonic counters reject signed but outdated images; this choice fits the scenario because the team must prevent an attacker downgrading firmware to a known-vulnerable version.
Incorrect Answers
A:Trusted enrollment injects unique credentials and records device identity before field deployment; it could help someone trying to prevent cloning when devices initially receive certificates and keys, but the problem is instead to prevent an attacker downgrading firmware to a known-vulnerable version.
C:Authenticated update packages must pass trusted signature checks before being accepted; a team would select it to stop modified update images from being installed on connected devices, which does not provide the particular result to prevent an attacker downgrading firmware to a known-vulnerable version.
D:Managed credential lifecycle limits exposure of secrets across widely deployed embedded fleets; its operational purpose is to replace long-lived device secrets without visiting every remote site, not to achieve the specific requirement to prevent an attacker downgrading firmware to a known-vulnerable version.
Question 402
To protect device identities in a dedicated security element, which control achieves the target outcome?
- Firmware signature verification
- Hardware root of trust
- OTA rollback protection
- Secure boot on IoT
Explanation
Correct Answer
B:Secure key storage separates private material from easily modified application firmware; this mechanism directly supports the requirement to protect device identities in a dedicated security element.
Incorrect Answers
A:Authenticated update packages must pass trusted signature checks before being accepted; although relevant to stop modified update images from being installed on connected devices, it does not by itself achieve the required task to protect device identities in a dedicated security element.
C:Anti-rollback metadata or monotonic counters reject signed but outdated images; that is useful when the task is to prevent an attacker downgrading firmware to a known-vulnerable version, not the stated requirement to protect device identities in a dedicated security element.
D:Hardware-rooted verification checks signed boot components before untrusted code is executed; a team would select it to reject unauthorized firmware during appliance startup, which does not provide the particular result to protect device identities in a dedicated security element.
Question 403
To replace long-lived device secrets without visiting every remote site, which solution should be adopted?
- Unique device certificates
- Hardware root of trust
- Credential rotation protocol
- Secure manufacturing provisioning
Explanation
Correct Answer
C:Managed credential lifecycle limits exposure of secrets across widely deployed embedded fleets; it supplies the specific control needed to replace long-lived device secrets without visiting every remote site.
Incorrect Answers
A:Device-specific certificates permit targeted revocation when one endpoint is compromised; the outcome it supports is to authenticate individual sensors without a shared fleet secret, whereas this scenario asks defenders to replace long-lived device secrets without visiting every remote site.
B:Secure key storage separates private material from easily modified application firmware; although relevant to protect device identities in a dedicated security element, it does not by itself achieve the required task to replace long-lived device secrets without visiting every remote site.
D:Trusted enrollment injects unique credentials and records device identity before field deployment; that is useful when the task is to prevent cloning when devices initially receive certificates and keys, not the stated requirement to replace long-lived device secrets without visiting every remote site.
Question 404
To verify both a sensor and its hub before exchanging commands, which of the available controls is suitable?
- Hardware root of trust
- Mutual authentication at gateway
- Secure manufacturing provisioning
- Secure boot on IoT
Explanation
Correct Answer
B:Two-sided identity checks limit impersonation by rogue devices or counterfeit controllers; that is why it addresses the operational task to verify both a sensor and its hub before exchanging commands.
Incorrect Answers
A:Secure key storage separates private material from easily modified application firmware; its mechanism supports protect device identities in a dedicated security element, while the requested control must be able to verify both a sensor and its hub before exchanging commands.
C:Trusted enrollment injects unique credentials and records device identity before field deployment; although relevant to prevent cloning when devices initially receive certificates and keys, it does not by itself achieve the required task to verify both a sensor and its hub before exchanging commands.
D:Hardware-rooted verification checks signed boot components before untrusted code is executed; it could help someone trying to reject unauthorized firmware during appliance startup, but the problem is instead to verify both a sensor and its hub before exchanging commands.
Question 405
To prevent cloning when devices initially receive certificates and keys and to identify devices running an unexpected image after scheduled maintenance, which TWO measures should the defender select? Choose TWO.
- Secure manufacturing provisioning
- Firmware hash inventory
- OTA rollback protection
- Mutual authentication at gateway
- Hardware root of trust
Explanation
Correct Answers
A:Trusted enrollment injects unique credentials and records device identity before field deployment; this is the measure that can prevent cloning when devices initially receive certificates and keys as one of the separately stated outcomes.
B:Trusted firmware measurements distinguish authorized versions from unauthorized changes; this is the measure that can identify devices running an unexpected image after scheduled maintenance as one of the separately stated outcomes.
Incorrect Answers
C:Anti-rollback metadata or monotonic counters reject signed but outdated images; the outcome it supports is to prevent an attacker downgrading firmware to a known-vulnerable version, whereas this scenario asks defenders to prevent cloning when devices initially receive certificates and keys and to identify devices running an unexpected image after scheduled maintenance.
D:Two-sided identity checks limit impersonation by rogue devices or counterfeit controllers; although relevant to verify both a sensor and its hub before exchanging commands, it does not by itself achieve the required task to prevent cloning when devices initially receive certificates and keys and to identify devices running an unexpected image after scheduled maintenance.
E:Secure key storage separates private material from easily modified application firmware; it could help someone trying to protect device identities in a dedicated security element, but the problem is instead to prevent cloning when devices initially receive certificates and keys and to identify devices running an unexpected image after scheduled maintenance.
Question 406
To identify devices running an unexpected image after scheduled maintenance, which approach should a IoT security operator choose?
- Secure manufacturing provisioning
- Mutual authentication at gateway
- Secure debug-interface disablement
- Firmware hash inventory
Explanation
Correct Answer
D:Trusted firmware measurements distinguish authorized versions from unauthorized changes; the requested outcome is precisely to identify devices running an unexpected image after scheduled maintenance.
Incorrect Answers
A:Trusted enrollment injects unique credentials and records device identity before field deployment; it addresses the different need to prevent cloning when devices initially receive certificates and keys, leaving the requested ability to identify devices running an unexpected image after scheduled maintenance unresolved.
B:Two-sided identity checks limit impersonation by rogue devices or counterfeit controllers; the technique works for situations involving verify both a sensor and its hub before exchanging commands, rather than this need to identify devices running an unexpected image after scheduled maintenance.
C:Production lockdown reduces physical extraction paths while retaining controlled servicing options; its mechanism supports prevent field attackers reading secrets through exposed JTAG or UART access, while the requested control must be able to identify devices running an unexpected image after scheduled maintenance.
Question 407
To prevent field attackers reading secrets through exposed JTAG or UART access, which approach should a IoT security operator choose?
- Secure manufacturing provisioning
- Firmware hash inventory
- Credential rotation protocol
- Secure debug-interface disablement
Explanation
Correct Answer
D:Production lockdown reduces physical extraction paths while retaining controlled servicing options; this choice fits the scenario because the team must prevent field attackers reading secrets through exposed JTAG or UART access.
Incorrect Answers
A:Trusted enrollment injects unique credentials and records device identity before field deployment; applying it would serve prevent cloning when devices initially receive certificates and keys without directly satisfying the goal to prevent field attackers reading secrets through exposed JTAG or UART access.
B:Trusted firmware measurements distinguish authorized versions from unauthorized changes; it addresses the different need to identify devices running an unexpected image after scheduled maintenance, leaving the requested ability to prevent field attackers reading secrets through exposed JTAG or UART access unresolved.
C:Managed credential lifecycle limits exposure of secrets across widely deployed embedded fleets; the technique works for situations involving replace long-lived device secrets without visiting every remote site, rather than this need to prevent field attackers reading secrets through exposed JTAG or UART access.
Question 408
To stop a compromised smart thermostat reaching payroll servers, which method is designed for the task?
- Zigbee network key management
- IoT network segmentation
- CoAP DTLS security
- MQTT TLS transport
Explanation
Correct Answer
B:Dedicated VLANs and inter-zone policy constrain embedded-device movement into enterprise systems; this mechanism directly supports the requirement to stop a compromised smart thermostat reaching payroll servers.
Incorrect Answers
A:Secure joining and key rotation limit unauthorized access to supported Zigbee networks; its operational purpose is to reduce exposure when a low-power mesh network shared key is compromised, not to achieve the specific requirement to stop a compromised smart thermostat reaching payroll servers.
C:DTLS can provide peer authentication and confidentiality for UDP communication under compatible stacks; it addresses the different need to protect datagram-based constrained-device application traffic, leaving the requested ability to stop a compromised smart thermostat reaching payroll servers unresolved.
D:TLS encrypts and authenticates MQTT transport when the client validates the broker certificate; the technique works for situations involving protect sensor messages sent to a broker over an untrusted link, rather than this need to stop a compromised smart thermostat reaching payroll servers.
Question 409
To protect sensor messages sent to a broker over an untrusted link, what technique should the team use?
- Bluetooth LE secure pairing
- MQTT topic authorization
- IoT network segmentation
- MQTT TLS transport
Explanation
Correct Answer
D:TLS encrypts and authenticates MQTT transport when the client validates the broker certificate; it supplies the specific control needed to protect sensor messages sent to a broker over an untrusted link.
Incorrect Answers
A:Authenticated pairing and bonding choose protections appropriate to device capabilities and threat model; a team would select it to mitigate unauthorized connection to nearby battery-powered sensors, which does not provide the particular result to protect sensor messages sent to a broker over an untrusted link.
B:Broker ACLs restrict which identities may publish or subscribe to designated topics; its operational purpose is to stop a low-privilege publisher writing commands to actuator topics, not to achieve the specific requirement to protect sensor messages sent to a broker over an untrusted link.
C:Dedicated VLANs and inter-zone policy constrain embedded-device movement into enterprise systems; applying it would serve stop a compromised smart thermostat reaching payroll servers without directly satisfying the goal to protect sensor messages sent to a broker over an untrusted link.
Question 410
To stop a low-privilege publisher writing commands to actuator topics, which protective or investigative measure applies?
- CoAP DTLS security
- MQTT topic authorization
- MQTT TLS transport
- Bluetooth LE secure pairing
- IoT network segmentation
Explanation
Correct Answer
B:Broker ACLs restrict which identities may publish or subscribe to designated topics; that is why it addresses the operational task to stop a low-privilege publisher writing commands to actuator topics.
Incorrect Answers
A:DTLS can provide peer authentication and confidentiality for UDP communication under compatible stacks; that is useful when the task is to protect datagram-based constrained-device application traffic, not the stated requirement to stop a low-privilege publisher writing commands to actuator topics.
C:TLS encrypts and authenticates MQTT transport when the client validates the broker certificate; its operational purpose is to protect sensor messages sent to a broker over an untrusted link, not to achieve the specific requirement to stop a low-privilege publisher writing commands to actuator topics.
D:Authenticated pairing and bonding choose protections appropriate to device capabilities and threat model; applying it would serve mitigate unauthorized connection to nearby battery-powered sensors without directly satisfying the goal to stop a low-privilege publisher writing commands to actuator topics.
E:Dedicated VLANs and inter-zone policy constrain embedded-device movement into enterprise systems; it addresses the different need to stop a compromised smart thermostat reaching payroll servers, leaving the requested ability to stop a low-privilege publisher writing commands to actuator topics unresolved.