DP-100 · Question #319
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. The proposed solution starting with 'Cre' does not correctly update an existing attached Synapse Spark Compute to use a user-assigned managed identity via Python SDK v2.
Question
Options
- AYes
- BNo
How the community answered
(52 responses)- A8% (4)
- B92% (48)
Why each option
The proposed solution starting with 'Cre' does not correctly update an existing attached Synapse Spark Compute to use a user-assigned managed identity via Python SDK v2.
The proposed 'Cre' solution does not complete the required steps to pass a user-assigned identity configuration to the existing Synapse Spark Compute update call, so it does not meet the goal.
Updating an attached Synapse Spark Compute's identity in SDK v2 requires passing a ManagedIdentityConfiguration object - with type set to 'user_assigned' and the target client ID - directly to the identity parameter of the compute object before calling begin_create_or_update. A solution that only creates an object without properly passing it through the update call does not apply the identity change to the existing compute.
Concept tested: Updating Synapse Spark Compute identity with SDK v2
Source: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-identity-based-service-authentication
Topics
Community Discussion
No community discussion yet for this question.