AZ400-Q: query a post-deployment error spike
After a deployment, error rate rises only for one application version. The team needs to isolate the affected version and top failing operation from collected telemetry. What should it use?
- A) A KQL query over the relevant telemetry/log tables filtered and grouped by deployment/version and operation. ✓
- B) An Azure resource lock.
- C) A new Git branch with no code changes.
- D) A storage redundancy change.
Answer: A. KQL can filter and aggregate collected telemetry to compare failures by version, operation, time, and other dimensions.
Why not the others: Locks, branches, and storage redundancy do not analyze operational telemetry.