DP-100 · Question #325
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 A. Yes. Passing a correctly configured ManagedIdentityConfiguration with the user_assigned_identity_client_id to the Synapse Spark Compute update call is the proper SDK v2 method for switching to user-assigned identity.
Question
Options
- AYes
- BNo
How the community answered
(60 responses)- A77% (46)
- B23% (14)
Why each option
Passing a correctly configured ManagedIdentityConfiguration with the user_assigned_identity_client_id to the Synapse Spark Compute update call is the proper SDK v2 method for switching to user-assigned identity.
In Azure ML Python SDK v2, you pass a ManagedIdentityConfiguration instance - with type='user_assigned' and the user_assigned_identity_client_id of the target Azure managed identity - to the identity parameter of a SynapseSparkCompute object, then call ml_client.compute.begin_create_or_update to apply the change. This is the documented pattern for replacing a system-assigned identity on an attached compute with a user-assigned one.
The 'Pas' solution does correctly supply a user-assigned ManagedIdentityConfiguration through the proper SDK v2 update pathway, so returning 'No' is incorrect.
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.