nerdexam
Network_Appliance

NS0-157 · Question #234

A storage administrator create a Quality of Service ( QoS) policy named pgMB300 which sets a maximum throughput of 300MB/s, and a second Quality of Service policy named pglO200 which sets the…

The correct answer is D. The attempt will fail. You cannot nest policy groups in any manner. In ONTAP, QoS policy groups cannot be nested - once a QoS policy is applied to a Vserver, no child storage object within that Vserver can be assigned a separate QoS policy.

Performance, Troubleshooting, and Security

Question

A storage administrator create a Quality of Service ( QoS) policy named pgMB300 which sets a maximum throughput of 300MB/s, and a second Quality of Service policy named pglO200 which sets the maximum throughput to 200 IOPS. The storage administrator assigns the pgMB300 QoS policy to Vserver vs1. The storage administrator then attempts to assign the pglO200 QOS policy to vol1 of vs1. What is the outcome?

Options

  • AThe attempt will succeed. You can assign Qos policy to storage object so long as single object
  • BThe attempt will fail. You cannot have policies with differently maximum throughput units. They all
  • CThe attempt will succeed. You can nest IOPS policy limit instead a MB/s policy limit.
  • DThe attempt will fail. You cannot nest policy groups in any manner.

How the community answered

(38 responses)
  • A
    26% (10)
  • B
    16% (6)
  • C
    8% (3)
  • D
    50% (19)

Why each option

In ONTAP, QoS policy groups cannot be nested - once a QoS policy is applied to a Vserver, no child storage object within that Vserver can be assigned a separate QoS policy.

AThe attempt will succeed. You can assign Qos policy to storage object so long as single object

ONTAP does not permit a child object to hold its own QoS policy when a parent object already has one assigned; nesting is not allowed under any condition.

BThe attempt will fail. You cannot have policies with differently maximum throughput units. They all

The failure is not caused by mismatched throughput units (MB/s vs IOPS); the failure is caused by the nesting restriction itself.

CThe attempt will succeed. You can nest IOPS policy limit instead a MB/s policy limit.

ONTAP does not support nesting an IOPS policy inside an MB/s policy; the nesting restriction applies universally regardless of unit type.

DThe attempt will fail. You cannot nest policy groups in any manner.Correct

ONTAP enforces a flat QoS policy assignment model where nesting is explicitly prohibited. Because pgMB300 is already assigned to vs1, assigning pglO200 to vol1 (a child of vs1) is blocked by the system, regardless of whether the throughput units differ.

Concept tested: ONTAP QoS policy group nesting restriction

Source: https://docs.netapp.com/us-en/ontap/performance-admin/assign-policy-group-task.html

Topics

#QoS#policy group nesting#IOPS#throughput MB/s

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full NS0-157 Practice