R1 #sh ip sla configuration - IP SLAs Infrastructure Engine-III Entry number: 1 - Owner: Tag: Operation timeout (millis

[answerhappygod]

R1 #sh ip sla configuration -
IP SLAs Infrastructure Engine-III

Entry number: 1 -
Owner:
Tag:
Operation timeout (milliseconds): 1000
Type of operation to perform: icmp-echo
Target address/Source address: 10.1.2.2/0.0.0.0
Request size (ARR data portion): 28

Verify data: No -
Vrf name:
Schedule:
Operation frequency (seconds): 2 (not considered if randomly scheduled)
Next Scheduled Start Time: Pending trigger

Group Scheduled: FALSE -

Randomly Scheduled: FALSE -

Life (seconds): 3600 -

Entry Ageout (seconds): never -
Recurring (Starting Everyday): False
Status of Entry (SSMP RowStatus): notInService

Threshold (milliseconds): 2000 -
Distribution statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
Enhanced history:
History statistics:

Number of history Lives kept: 0 -
Number of history Buckets kept: 15

History Filter Type: None -

R1 # sh ip sla statistics -
IPSLAs Latest Operation Statistics

IPSLA operation id: 1 -

Number of successes: Unknown -

Number of failures: Unknown -

Operation time to live: 0 -
Refer to the exhibit. For which reason could the statistics for IP SLA operation 1 be unknown?

A. The IP SLA schedule is missing.
B. The ICMP echoes were lost in transit.
C. The Type of Service parameter is configured incorrectly.
D. The Operation Frequency value is the same as the Operation Timeout value.
E. Data verification has been disabled.