Configure monitoring for a DevOps environment

Elmstead Insurance has a log search alert rule named alr-claims-exceptions that fires when the exceptions table for the workspace-based Application Insights resource appi-claims-prod shows more than 50 exceptions in 5 minutes. Each time the alert fires, a Bug must be created automatically in the Azure Boards project Claims, assigned to the Claims API area path, with the alert details in the description. You must minimize custom code.

What should you do?

1. AAdd an action to the alert rule's action group that runs a Logic App workflow, and use the Azure DevOps connector in the workflow to create the Bug.Action groups can trigger a Logic App with the common alert schema payload, and the Azure DevOps connector creates the work item without custom code.
2. BIn the Claims project, create a service hook subscription that listens for Work item created events and sends them to Azure Monitor.Service hooks publish Azure DevOps events to external services; they do not receive Azure Monitor alerts or create work items from them.
3. CAdd an ITSM action to the action group that targets the Claims project.The ITSM action integrates with IT service management tools such as ServiceNow; it does not create Azure Boards work items.
4. DConfigure Application Insights work item integration on appi-claims-prod for the Claims project.Work item integration lets a person create a work item from a telemetry item in the portal; it does not create one automatically when an alert fires.

Corvane Health runs an AKS cluster named aks-corvane-prod with Container Insights enabled, sending data to a Log Analytics workspace named law-corvane. A cost review shows that most ContainerLogV2 ingestion comes from stdout and stderr of pods in the qa-sandbox and load-test namespaces, which nobody queries. You must stop that data from being ingested while keeping logs from all other namespaces. Minimize cost.

What should you do?

1. AReduce the retention of the ContainerLogV2 table in law-corvane to 4 days.Shorter retention lowers storage cost, but every log line is still ingested and billed at ingestion time.
2. BDeploy the container-azm-ms-agentconfig ConfigMap to aks-corvane-prod with exclude_namespaces set to qa-sandbox and load-test in the log_collection_settings.stdout and log_collection_settings.stderr sections.The ConfigMap is the supported way to filter container logs sent to ContainerLogV2 by namespace; the agent stops collecting those logs at the source, so they are never ingested or billed.
3. CIn the Container Insights data collection rule for aks-corvane-prod, set namespaceFilteringMode to Exclude and list qa-sandbox and load-test in namespaces.Namespace filtering in the data collection rule applies to inventory and performance data such as KubePodInventory and Perf; it doesn't apply to data sent to ContainerLogV2, which can only be filtered with the ConfigMap.
4. DRemove the VM Insights data collection rule association from the node pool virtual machine scale sets.VM Insights rules collect guest performance data into InsightsMetrics; container logs come from the Container Insights rule and agent, not from VM Insights.

Hollins Analytics tracks its work in a GitHub project named Mobile Roadmap that has a single-select Status field (Todo, In progress, Done) and an Iteration field with two-week sprints. The delivery lead wants a chart, saved in the project, that shows for each sprint how many items are in each status. The chart must update automatically as items move.

What should you do?

1. AIn Mobile Roadmap, open Insights, create a new chart, set the layout to Stacked column, set the X-axis to Iteration, and group by Status.Project insights charts are saved with the project, built from live project data, and can use custom fields such as Iteration for the X-axis and Status for grouping.
2. BOpen the repository Insights tab and use Pulse filtered to the last two weeks.Pulse summarizes repository activity for a period; it cannot chart project items by custom fields such as Iteration and Status.
3. COpen the Actions usage metrics for the organization and group the results by workflow.Actions usage metrics report workflow minutes and job runs, not the status of project items.
4. DCreate a board view in Mobile Roadmap grouped by Status and filter it to the current iteration.A board view lists items by column for one filter at a time; it is not a chart and does not compare all sprints side by side.

Pellmoor Robotics hosts its firmware in a GitHub repository named pellmoor/motor-control. Every Monday the engineering manager wants a quick summary of the previous week: how many pull requests were merged and opened, how many issues were closed and opened, and who contributed. No additional tooling or configuration should be required.

Which GitHub feature should the manager use?

1. AThe Traffic graph under the repository Insights tab.Traffic shows views, unique visitors, clones, and referring sites, not pull request or issue activity.
2. BThe Dependency graph under the repository Insights tab.The dependency graph lists the packages the repository depends on and its dependents; it does not summarize activity.
3. CPulse under the repository Insights tab, with the period set to 1 week.Pulse summarizes merged and proposed pull requests, closed and new issues, and contributor activity for a selected period.
4. DThe Contributors graph under the repository Insights tab.The Contributors graph shows commits per contributor over time but does not summarize pull requests and issues.