A healthy test session has periodic connection-network records but no ConnectionGraphicsData records. The analyst wants a regular baseline of healthy sessions. Which approach is appropriate?

✓ Correct answer

• Use periodic network records and relevant host metrics rather than assuming graphics logging is broken

The tables have different collection behavior. A healthy baseline needs regularly collected network and workload evidence, not mandatory graphics rows. Option explanations: A. Artificially reduce bandwidth so every baseline session becomes unhealthy: Introducing a fault does not produce a representative healthy baseline. B. Use periodic network records and relevant host metrics rather than assuming graphics logging is broken: Graphics data is degradation-oriented and is not a continuous baseline of healthy sessions. C. Use only profile-file sizes as graphical latency measurements: Stored size is not a measurement of encoding, transport, decoding or rendering delay. D. Treat missing graphics rows as proof the user never connected: The connection-network records already establish an active monitored connection. Sources: Analyze connection quality in Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/connection-latency

Read the source reference