AZ-400: Implement an Instrumentation Strategy Competency (Intermediate Level)

  • 24m
  • 24 questions
The Implement an Instrumentation Strategy Competency (Intermediate Level) benchmark assesses your ability to implement effective instrumentation strategies for software development. You will be evaluated on your ability to collect and analyze data from different sources, monitor performance and usage, and optimize system behavior and user experience. You will also be evaluated on your skills in implementing instrumentation strategies that include monitoring and logging tools, telemetry data collection, and analysis techniques. Learners who score high on this benchmark demonstrate that they have the ability to implement effective instrumentation strategies. This competency is essential for software development teams to monitor and optimize system performance, improve user experience, and ensure continuous improvement.

Topics covered

  • administer alerts using appropriate metrics
  • analyze system dependencies to determine which dependency should be included in health check
  • calculate healthy response timeouts based on service-level objectives (SLOs) for the service
  • calculate when a system will fail under various conditions
  • configure and integrate additional monitoring tools
  • configure and integrate container monitoring
  • define the elements of predictive maintenance
  • design a log aggregation and query strategy
  • design an approach for partial health situations
  • execute alerts based on application health checks
  • identify a communication mechanism to notify users of degraded systems
  • identify and recommend metrics on which to base alerts
  • identify the purpose and use of user analytics
  • implement alerts based on appropriate log messages
  • implement alerts for self-healing activities
  • implement different types of health checks
  • implement distributed tracing
  • inspect application performance indicators
  • integrate user analytics
  • interrogate Log Analytics logs using basic Kusto (KQL) queries
  • manage access control to logs
  • measure baseline metrics for system
  • outline the role of continuously performing application, infrastructure, and storage logging
  • recall how to design distributed tracing