In the context of Juniper Mist, which two statements describe a bad user minute? (Choose two.)

In the Juniper Mist platform, "Bad User Minutes" is a key metric used to quantify the impact of network issues on end-users. It is not merely a count of connection time but a method to normalize the severity of a problem. The calculation multiplies the number of users experiencing a service failure (i.e., failing to meet a Service Level Expectation) by the duration in minutes of that failure. This provides a standardized value that reflects the collective negative experience, allowing administrators to prioritize issues that affect the most users for the longest time.

A. This describes total connection time, not a metric for a negative experience.

C. This is too specific to a "device" being down; bad user minutes can result from performance degradation without a device failure.

Juniper Mist Documentation, "Marvis - Actions," Section: Root Cause Analysis. This document states, "Bad User Minutes—The number of users affected by an issue, multiplied by the number of minutes they were affected."

Juniper Mist Documentation, "Service Levels," Section: Service Level Details. This page explains, "Bad user minutes provide a way to normalize the negative experience of users on your network."