Microsoft Azure Architect Design (AZ-301) Practice Exam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Microsoft Azure Architect Design (AZ-301) Exam with interactive quizzes featuring flashcards and multiple-choice questions, each packed with hints and explanations to ace your certification test!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


What is the recommended solution for adding external developers to the Contributor role in an Azure subscription?

  1. Create service accounts for the developers

  2. Create guest accounts in the Azure AD tenant

  3. Assign the role through Azure DevOps

  4. Invite developers to join Office 365 groups

The correct answer is: Create guest accounts in the Azure AD tenant

Creating guest accounts in the Azure Active Directory (Azure AD) tenant is the recommended solution for adding external developers to the Contributor role in an Azure subscription. This approach allows external developers to be securely integrated into the Azure environment while maintaining control over their access and permissions. When you create guest accounts, you can give these external users specific roles and permissions without needing to create separate service accounts or compromising the security of your system. This method also ensures that external collaborators adhere to the policies set within your Azure environment. By leveraging Azure AD, guest users can utilize their existing accounts from other services like Google or their work emails, which simplifies the onboarding process. Furthermore, integrating external users as guests within your Azure AD allows for better monitoring and governance of their activities, as access permissions can be managed and audited through Azure's role-based access control (RBAC) system. The accountability and traceability offered through guest accounts make this the best practice for collaborating with external developers. This solution stands out alongside the other options. For instance, creating service accounts could lead to unnecessary complexity and the need for additional account management, while assigning roles through Azure DevOps would not give external users the necessary access at the subscription level. Inviting developers to join Office 365 groups might not directly