300-415 · Question #207
policy sla-class BULK_DATA loss 20 latency 300 jitter 100 ! sla-class TRANSACTIONAL_DATA loss 15 latency 50 jitter 100 ! sla-class REALTIME loss 20 latency 100 jitter 30 ! app-route-policy…
The correct answer is B. sla-class TRANSACTIONAL_DATA loss 5 latency 50 jitter 100 ! sla-class REALTIME loss 2 latency 100 jitter 30 ! The provided SLA classes for REALTIME and TRANSACTIONAL_DATA in the app-route-policy are unrealistically high for loss, and Option B corrects these values to typical industry standards.
Question
Options
- Asla-class BULK_DATA loss 15 latency 100 jitter 100 ! sla-class TRANSACTIONAL_DATA loss 10 latency 300 jitter 100 !
- Bsla-class TRANSACTIONAL_DATA loss 5 latency 50 jitter 100 ! sla-class REALTIME loss 2 latency 100 jitter 30 !
- Csla-class TRANSACTIONAL_DATA loss 2 latency 100 jitter 100 ! sla-class REALTIME loss 15 latency 100 jitter 100 !
- Dsla-class BULK_DATA loss 10 latency 300 jitter 100 ! sla-class REALTIME loss 2 latency 100 jitter 30 !
How the community answered
(29 responses)- A3% (1)
- B83% (24)
- C10% (3)
- D3% (1)
Why each option
The provided SLA classes for REALTIME and TRANSACTIONAL_DATA in the app-route-policy are unrealistically high for loss, and Option B corrects these values to typical industry standards.
Option A increases the latency requirement for 'TRANSACTIONAL_DATA' from 50ms to 300ms, which is detrimental and inappropriate for transactional applications.
The initial policy's 'sla-class REALTIME' definition, with an allowable 'loss 20', is excessively high and inappropriate for real-time applications, which demand minimal packet loss. Similarly, 'sla-class TRANSACTIONAL_DATA' with 'loss 15' is also loose. Option B corrects these critical parameters by setting 'loss 5' for 'TRANSACTIONAL_DATA' and 'loss 2' for 'REALTIME', aligning them with typical performance requirements for these traffic types and making the policy effective for optimizing application performance.
Option C increases the latency for 'TRANSACTIONAL_DATA' from 50ms to 100ms and significantly degrades the 'REALTIME' class by increasing its loss to 15% and jitter to 100ms, making it unsuitable.
While Option D correctly lowers the 'REALTIME' loss, it also modifies 'BULK_DATA', which is not utilized in the provided 'app-route-policy', and does not address the high loss value for 'TRANSACTIONAL_DATA' which is used.
Concept tested: Cisco SD-WAN SLA Class Definition and Optimization
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/sdwan-policy-config.html#_Define_SLA_Classes_for_Application_Aware_Routing
Topics
Community Discussion
No community discussion yet for this question.