Design identity, governance, and monitoring solutions

1. Which alert type runs a KQL query on logs and fires when the results meet a condition?

1. Log search alert rule
2. Metric alert
3. Budget alert
4. Service Health alert

2. Personal data must be removed from logs before they are stored in the Log Analytics workspace. What should you design?

1. An action group
2. An ingestion-time transformation in a data collection rule
3. A log alert rule that deletes matching rows every hour
4. A workbook

3. Operations must find which configuration changes were made to resources across subscriptions in the last 14 days. Which tool fits?

1. Application Insights live metrics for every application
2. Azure Resource Graph resource changes
3. Azure Advisor
4. Service Health

4. Which service provides just-in-time, approval-based activation of Azure resource roles such as Owner?

1. Microsoft Entra access reviews
2. Azure RBAC custom roles
3. Azure Lighthouse
4. Microsoft Entra Privileged Identity Management

5. A partner organization's employees need access to an internal app using their own corporate credentials. Which approach should you recommend?

1. Create local accounts for each partner user
2. Microsoft Entra B2B collaboration with guest users
3. Use Microsoft Entra Domain Services
4. Publish it with Application Proxy and anonymous access

6. Which approach should be used so that an Azure DevOps pipeline deploys to Azure without storing secrets?

1. Anonymous access
2. A long-lived client secret in the repo
3. A shared admin password
4. A service connection using workload identity federation

7. Which Azure Policy effect automatically deploys a resource such as a diagnostic setting when a matching resource is created?

1. Append
2. Deny
3. DeployIfNotExists
4. AuditIfNotExists only

8. Which resource organization design is recommended to separate production and non-production workloads with different governance?

1. Separate subscriptions under management groups with their own policies
2. One resource group for all workloads, with tags that mark each environment
3. One shared VM for every environment
4. Tags only on one shared subscription, with a naming convention per environment