Hotspot Question You have an Azure subscription. From Entitlement management, you plan to create a catalog named Catalog1 that will contain a custom extension. What should you create first, and what…

Question

Answer Area

• First create:An Azure logic app
  A managed accountAn Azure Automation accountAn Azure logic app
• Distribute Catalog1 by using:An access package
  A playbookA workflowAn access package

• A managed account|An access package
  100% (1)

Explanation

To implement a custom extension for an Azure Entitlement Management catalog, an Azure Logic App should be created first, and the catalog's resources are distributed via an access package.

Approach. The question asks what to create first for a custom extension within Entitlement management and how to distribute Catalog1.

1. First create: An Azure logic app

   • Azure AD Entitlement Management supports custom extensions to integrate custom workflows during the access package request/assignment lifecycle. These custom extensions are typically implemented using Azure Logic Apps. Logic Apps provide a serverless platform for building automated workflows, making them ideal for executing custom code or actions based on events within Entitlement Management.

2. Distribute Catalog1 by using: An access package

   • In Azure AD Entitlement Management, a 'Catalog' is a container of resources and access packages. 'Access packages' are the fundamental units for grouping resources (like applications, groups, SharePoint sites, and custom extensions) and defining policies for how users gain access to them. Users request access to an access package, which then provisions them access to all included resources. Therefore, an access package is the mechanism used to distribute the content (including custom extensions) of a catalog to users.

Common mistakes.

• common_mistake. For 'First create:', selecting 'An Azure Automation account' is incorrect because while it can perform automation, Azure Logic Apps are the recommended and more integrated solution for implementing custom extensions in Azure AD Entitlement Management due to their event-driven workflow capabilities. 'A managed account' is too generic and doesn't specify an execution platform for custom logic.

For 'Distribute Catalog1 by using:', selecting 'A playbook' is incorrect as playbooks are typically associated with security automation (e.g., Azure Sentinel) and not for distributing access in Entitlement Management. 'A workflow' is too general a term; while access packages involve workflows, 'An access package' is the specific, defined object in Entitlement Management used for distribution and access granting.

Concept tested. Azure Active Directory Entitlement Management concepts, including Catalogs, Access Packages, and Custom Extensions. It also tests knowledge of Azure Logic Apps as a platform for serverless automation and custom workflow integration within Azure AD services.

Reference. https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-overview | https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-logic-app-tutorial

No community discussion yet for this question.