DP-100 · Question #320
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 'Ini' does not fulfill the requirement to update an existing Synapse Spark Compute from system-assigned to user-assigned managed identity via Python SDK v2.
Question
Options
- AYes
- BNo
How the community answered
(25 responses)- A24% (6)
- B76% (19)
Why each option
The proposed solution starting with 'Ini' does not fulfill the requirement to update an existing Synapse Spark Compute from system-assigned to user-assigned managed identity via Python SDK v2.
The proposed initialization-based solution does not call the update method with a user-assigned identity configuration on the existing Synapse Spark Compute, so it does not satisfy the requirement.
Switching an attached Synapse Spark Compute to user-assigned identity requires calling begin_create_or_update with a SynapseSparkCompute object whose identity field contains a properly configured ManagedIdentityConfiguration. An initialization-only step does not invoke the update API and therefore does not change the identity type on the running 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.