0
0
Rest APIprogramming~10 mins

SLA and uptime tracking in Rest API - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define the endpoint path for uptime status.

Rest API
GET /api/[1]/status
Drag options to blanks, or click blank then click option'
Auptime
Bhealth
Cmetrics
Dlogs
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'health' instead of 'uptime' which is more general.
Using 'logs' which is unrelated to uptime status.
2fill in blank
medium

Complete the code to specify the HTTP method for retrieving SLA data.

Rest API
[1] /api/sla/data
Drag options to blanks, or click blank then click option'
APOST
BGET
CPUT
DDELETE
Attempts:
3 left
💡 Hint
Common Mistakes
Using POST which is for sending data.
Using DELETE which removes data.
3fill in blank
hard

Fix the error in the JSON response key for uptime percentage.

Rest API
{
  "uptime_[1]": 99.95
}
Drag options to blanks, or click blank then click option'
Apercentile
Bpercent
Cpercentage
Dpercentages
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'percent' which is less descriptive.
Using 'percentile' which is a statistical term.
4fill in blank
hard

Fill both blanks to filter SLA records by minimum uptime and sort order.

Rest API
GET /api/sla/records?min_uptime=[1]&sort=[2]
Drag options to blanks, or click blank then click option'
A99.9
Bdesc
Casc
D100
Attempts:
3 left
💡 Hint
Common Mistakes
Using 100 as minimum uptime which is too strict.
Using 'desc' when ascending order is expected.
5fill in blank
hard

Fill all three blanks to create a JSON payload for updating SLA thresholds.

Rest API
{
  "[1]": [2],
  "[3]": 99.99
}
Drag options to blanks, or click blank then click option'
Amin_uptime
Bthreshold
Cmax_downtime
D100
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing 'threshold' with key names.
Using wrong numeric values.