Question 610
The HPE AOS-CX switching case is: A bulk database replication job is trusted as high priority and causes phone jitter during office hours. Which TWO choices together provide the targeted remedy and independent validation? (Select TWO.)
Explanation
Correct Answers
The targeted correction for A bulk database replication job is trusted as high priority and causes phone jitter during office hours is: Compare ingress class, remarking, egress queue and scheduling to identify the real congestion and fairness defect. It reduces the risk that an incorrect high-priority class can starve the intended protected service during busy periods.
A separate operational validation for A bulk database replication job is trusted as high priority and causes phone jitter during office hours is: Packet captures and class drop counters show expected markings and acceptable loss and latency with congestion reproduced. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns control-plane resource saturation and high cpu; its associated risk is: A storm of protocol events or excessive polling can delay management and routing convergence despite sufficient data-plane bandwidth. The observed case A bulk database replication job is trusted as high priority and causes phone jitter during office hours requires the more specific qos misclassification and queue starvation control. The targeted action is: Compare ingress class, remarking, egress queue and scheduling to identify the real congestion and fairness defect.
This alternative concerns end-node and application-path performance differentiation; its associated risk is: Local client faults and server slowness can resemble network degradation, causing disruptive configuration changes that do not help. The observed case A bulk database replication job is trusted as high priority and causes phone jitter during office hours requires the more specific qos misclassification and queue starvation control. The targeted action is: Compare ingress class, remarking, egress queue and scheduling to identify the real congestion and fairness defect.
This alternative concerns mtu consistency and large-packet forwarding; its associated risk is: A mismatch can create fragmentation or loss and cause application timeouts even while basic ping succeeds. The observed case A bulk database replication job is trusted as high priority and causes phone jitter during office hours requires the more specific qos misclassification and queue starvation control. The targeted action is: Compare ingress class, remarking, egress queue and scheduling to identify the real congestion and fairness defect.