Microsoft Azure IoT Developer 온라인 연습
최종 업데이트 시간: 2024년11월08일
당신은 온라인 연습 문제를 통해 Microsoft AZ-220 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 AZ-220 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 60개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Each IoT Edge device runs at least two modules: $edgeAgent and $edgeHub, which are part of the IoT Edge runtime. IoT Edge device can run multiple additional modules for any number of processes. Use a deployment manifest to tell your device which modules to install and how to configure them to work together.
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-composition
정답:
Explanation:
AMQP over WebSockets uses port 443.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
정답:
Explanation:
An enrollment is the record of devices or groups of devices that may register through auto-provisioning. The enrollment record contains information about the device or group of devices, including:
the attestation mechanism used by the device
the optional initial desired configuration desired IoT hub the desired device ID
Note: Azure IoT auto-provisioning can be broken into three phases:
정답:
Explanation:
Text, letter
Description automatically generated
Box 1: $connectionModuled
Add a route that tells the edge hub to route any message received by the IoT Edge device that was not sent by an IoT Edge module.
Box 2: $upstream
Send messages to $upstream, which passes the messages to the connected IoT Hub.
정답:
Explanation:
The module twin for the IoT Edge agent is called $edgeAgent and coordinates the communications between the IoT Edge agent running on a device and IoT Hub. The desired properties are set when applying a deployment manifest on a specific device as part of a single-device or at-scale deployment.
These properties include: runtime.settings.registryCredentials.{registryId}.username runtime.settings.registryCredentials.registryId}.password
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-edgeagent-edgehub
정답:
Explanation:
C: To use the file upload functionality in IoT Hub, you must first associate an Azure Storage account with your hub. Select File upload to display a list of file upload properties for the IoT hub that is being modified.
For Storage container: Use the Azure portal to select a blob container in an Azure Storage account in your current Azure subscription to associate with your IoT Hub. If necessary, you can create an Azure Storage account on the Storage accounts blade and blob container on the Containers
A: IoT Hub has an endpoint specifically for devices to request a SAS URI for storage to upload a file. To start the file upload process, the device sends a POST request to {iot hub}.azure-devices.net/devices/{deviceId}/ files with the following JSON body:
{
"blobName": "{name of the file for which a SAS URI will be generated}"
}
Reference: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-hub/iot-hub-configure-file-upload.md
정답:
Explanation:
Graphical user interface, text, application, Word, email
Description automatically generated
Box 1: createOptions
Every module has a settings property that contains the module image, an address for the container image in a container registry, and any createOptions to configure the image on startup.
Box 2: portbindings
Use the PortBindings setting in the HostConfig group of the Docker container create options to map the exposed port in the module to a port on the host device.
For example, if you exposed port 8080 inside the module and want to map that to port 80 of the host device, the create options in the template.json file would look like the following example:
"createOptions": {
"HostConfig": {
"PortBindings": {
"8080/tcp": [
{
"HostPort": "80"
}
]
}
}
}
정답:
Explanation:
Execute az extension add --name azure-cli-iot-ext once and try again.
In order to read the telemetry from your hub by CLI, you have to enable IoT Extension with the following commands:
Add: az extension add --name azure-cli-iot-ext
Reference: https://github.com/MicrosoftDocs/azure-docs/issues/20843
정답:
Explanation:
The device telemetry category tracks errors that occur at the IoT hub and are related to the telemetry pipeline. This category includes errors that occur when sending telemetry events (such as throttling) and receiving telemetry events (such as unauthorized reader). This category cannot catch errors caused by code running on the device itself.
Note: The metric d2c.telemetry.ingress.sendThrottle is the number of throttling errors due to device throughput throttles.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-health
정답:
Explanation:
MQTT over WebSockets, AMQP over WebSocket, and HTTPS use port 443.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
정답:
Explanation:
Each device uses its derived device key with your unique registration ID to perform symmetric key attestation with the enrollment during provisioning. To generate the device key, use the key you copied from your DPS enrollment to compute an HMAC-SHA256 of the unique registration ID for the device and convert the result into Base64 format.
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-auto-provision-symmetric-keys
정답:
Explanation:
A common problem with many legacy devices is that they often have an identity that is composed of a single piece of information. This identity information is usually a MAC address or a serial number. Legacy devices may not have a certificate, TPM, or any other security feature that can be used to securely identify the device. The Device Provisioning Service for IoT hub includes symmetric key attestation. Symmetric key attestation can be used to identify a device based off information like the MAC address or a serial number.
Reference: https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-legacy-device-symm-key
정답:
Explanation:
Automated re-provisioning support.
Microsoft added first-class support for device re-provisioning which allows devices to be reassigned to a different IoT solution sometime after the initial solution assignment. Re-provisioning support is available in two options:
Factory reset, in which the device twin data for the new IoT hub is populated from the enrollment list instead of the old IoT hub. This is common for factory reset scenarios as well as leased device scenarios. Migration, in which device twin data is moved from the old IoT hub to the new IoT hub. This is common for scenarios in which a device is moving between geographies.
Reference: https://azure.microsoft.com/en-us/blog/new-year-newly-available-iot-hub-device-provisioning-service-features/
정답:
Explanation:
Box1: Yes
Box 2: Yes
Fanspeed 73 is a reported property.
Box 3: No
The deviceID property is read only.
정답:
Explanation:
2500* 6 KB * 12 = 180,000 KB/minute = 180 MB/Minute.
B3, S3 can handle up to 814 MB/minute per unit.
Incorrect Answers:
A, C: B1, S1 can only handle up to 1111 KB/minute per unit B: B2, S2 can only handle up to 16 MB/minute per unit.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-scaling