An administrator created a custom role scoped to a resource group RG1 in Sub1. You need to make that custom role assignable to any resource group in Sub1 and Sub2 while minimizing administrative effort. What should you do?

Custom roles in Azure have an assignableScopes property that defines where the role can be assigned. Initially, the role was scoped only to RG1. To make it assignable across Sub1 and Sub2, you must modify this property. By adding Sub1 and Sub2 to the assignableScopes array and removing RG1, the role becomes available for assignment at the subscription level for both Sub1 and Sub2, and consequently to any resource group within them. This directly addresses the requirement with minimal administrative effort as it involves modifying a single existing role. Creating new roles (options B, C, D) would be inefficient and increase management overhead.