AZ-220 Online Practice Questions and Answers

Correct Answer: B

Routes are declared in the $edgeHub desired properties.

Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-composition

Correct Answer: B

You can use Azure Active Directory (Azure AD) to authenticate requests to Azure IoT Hub service APIs, like create device identity and invoke direct method. You can also use Azure role-based access control (Azure RBAC) to authorize those same service APIs. By using these technologies together, you can grant permissions to access IoT Hub service APIs to an Azure AD security principal. This security principal could be a user, group, or application service principal.

Note: There are three different ways for controlling access to IoT Hub:

1.

Azure Active Directory (Azure AD) integration for service APIs. Azure provides identity-based authentication with AAD and fine-grained authorization with Azure role-based access control (Azure RBAC). Azure AD and RBAC integration is supported for IoT hub service APIs only.

2.

Shared access signatures lets you group permissions and grant them to applications using access keys and signed security tokens.

3.

Per-device security credentials. Each IoT Hub contains an identity registry For each device in this identity registry, you can configure security credentials that grant DeviceConnect permissions scoped to the that device's endpoints.

Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-dev-guide-azure-ad-rbac

Correct Answer:

Box 1: ResourceProvider ==

Query to monitor your IoT hub connectivity Errors: Identify device connection errors.

AzureDiagnostics

| where ResourceProvider == "MICROSOFT.DEVICES" and ResourceType == "IOTHUBS"

| where Category == "Connections" and Level == "Error"

Box 2: ResourceType ==

Box 3: Category ==

Reference:

https://docs.microsoft.com/en-us/azure/iot-hub/monitor-iot-hub

Correct Answer:

Step: With DPS (Device Provisioning Service) you can generate device credentials and configure the devices offline without registering the devices through IoT Central UI. Connect devices that use SAS tokens without registering

1.

Copy the IoT Central application's group primary key

2.

Use the dps-keygen tool to generate the device SAS keys. Use the group primary key from the previous step. The device IDs must be lower-case: dps-keygen -mk: -di:

3.

The OEM flashes each device with a device ID, a generated device SAS key, and the application ID scope value.

4.

When you switch on a device, it first connects to DPS to retrieve its IoT Central registration information.

The device initially has a device status Unassociated on the Devices page and isn't assigned to a device template. On the Devices page, Migrate the device to the appropriate device template. Device provisioning is now complete, the device

status is now Provisioned, and the device can start sending data.

On the Administration > Device connection page, the Auto approve option controls whether you need to manually approve the device before it can start sending data.

Reference:

https://docs.microsoft.com/en-us/azure/iot-central/core/concepts-get-connected

Correct Answer:

Correct Answer:

Correct Answer:

Correct Answer:

Reference: https://docs.microsoft.com/bs-cyrl-ba/azure/iot-hub/iot-hub-message-enrichments-overview