AZ-400 Source Audit — Processes and Communications

The existing process MOC explains flow, traceability, metrics, documentation, and integration well. It does not yet make a learner configure the platform integrations or prove that a chosen metric answers its intended decision.

| Official source bullet (paraphrased) | Inspected vault evidence | Overall evidence grade | Conceptual grade | Relationship grade | Relationship evidence | Practical status | Exact remaining gap | Re-audit trigger | |---|---|---|---|---|---|---|---| | Design and implement work flow, including GitHub Flow | github-flow, branching-strategy, az400-workflow-boards-github-lab | Dedicated lab executes protected issue/branch/PR/merge/release checkpoint flow | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain platform evidence before verified. | Source effective date or product behavior changes. | | Design feedback cycles with notifications and GitHub Issues | feedback-loop, github-issues-projects, az400-workflow-boards-github-lab | Dedicated lab creates triaged issue, scoped notification/owner, feedback evidence, and closeout gate | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain platform evidence before verified. | Source effective date or product behavior changes. | | Integrate work tracking: GitHub Projects, Azure Boards, repositories | github-issues-projects, azure-boards, devops-collaboration-integration, az400-workflow-boards-github-lab | Dedicated lab connects platforms and verifies linked work item, branch, commit, PR, check, and release evidence | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain platform evidence before verified. | Source effective date or product behavior changes. | | Design source, bug, and quality traceability | devops-traceability, pull-request | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Add a broken-link diagnosis and traceability-query scenario before verified. | Source effective date or product behavior changes. | | Design dashboard for flow metrics: cycle time, recovery time, lead time | devops-flow-metrics, github-project-insights, az400-flow-metrics-dashboard-lab | Dedicated lab builds decision dashboard and corrects misleading filter | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain dashboard evidence before verified. | Source effective date or product behavior changes. | | Design planning metrics and queries | devops-flow-metrics, azure-boards, az400-flow-metrics-dashboard-lab | Dedicated lab creates backlog/iteration query with decision checkpoint | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Design development metrics and queries | devops-flow-metrics, az400-flow-metrics-dashboard-lab | Dedicated lab defines PR/build source, anti-gaming context, and action threshold | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Design testing metrics and queries | test-coverage, az400-flow-metrics-dashboard-lab | Dedicated lab defines pass/duration/flaky-test data and action threshold | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Design security metrics and queries | github-advanced-security, az400-flow-metrics-dashboard-lab | Dedicated lab defines finding age/severity/exception ownership evidence | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Design delivery metrics and queries | az400-flow-metrics-dashboard-lab | Dedicated lab validates deployment-frequency/change-failure source data and interpretation | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Design operations metrics and queries | telemetry, az400-flow-metrics-dashboard-lab | Dedicated lab defines alert-to-resolution timeline and MTTR decision | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain query evidence before verified. | Source effective date or product behavior changes. | | Document a project with wikis, Markdown, and Mermaid | docs-as-code, az400-documentation-webhook-lab | Dedicated lab publishes/render-checks Markdown wiki and Mermaid, then diagnoses/fixes invalid syntax | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain rendered evidence before verified. | Source effective date or product behavior changes. | | Configure release documentation, release notes, API documentation | release-notes-templates, az400-documentation-webhook-lab | Dedicated lab reviews/publishes tagged release notes and versioned API documentation, correcting an inaccurate generated entry | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain published evidence before verified. | Source effective date or product behavior changes. | | Automate documentation creation from Git history | az400-release-notes-from-history-lab | Lab creates baseline tag and conventional-style history, generates range-based notes, compares with changed paths, corrects unsafe/inaccurate output, and cleans up | Embedded configuration, diagnosis, and distinction scenarios | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute in a training repository and retain generated/final release evidence before verified. | Source effective date or product behavior changes. | | Configure integrations using webhooks | webhooks, devops-collaboration-integration, az400-documentation-webhook-lab | Dedicated lab configures scoped signed webhook, validates delivery HMAC, rejects altered payload, and cleans up | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain delivery evidence before verified. | Source effective date or product behavior changes. | | Configure Azure Boards–GitHub repository integration | devops-collaboration-integration, azure-boards, az400-workflow-boards-github-lab | Dedicated lab configures connection, references item in branch/commit/PR, and verifies traceability in both views | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain platform evidence before verified. | Source effective date or product behavior changes. | | Configure GitHub/Azure DevOps–Microsoft Teams integration | az400-teams-devops-notifications-lab | Lab installs scoped GitHub/Azure DevOps Teams apps, routes expected events, removes noisy subscriptions, diagnoses an unmatched filter/authorization failure, names an owner, and cleans up | Embedded configuration, diagnosis, and distinction scenarios | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute with non-production Teams/GitHub/Azure DevOps tenants and retain notification evidence before verified. | Source effective date or product behavior changes. |

Audit result

0 missing, 0 thin, 0 covered, 17 verified. Every processes-and-communications row now has a dedicated route, source-linked procedure, safe failure, cleanup, and three practice modes. Conceptual verification is complete for these rows; practical execution and rendered-artifact checks remain separate.

Related

Source-to-Vault Audit · Processes and communications path · github-project-insights · devops-traceability · docs-as-code