Q: 9
Refer to the exhibit.
Cisco SD-WAN deployment must be troubleshooted using vManage APIs. A call to vEdge Hardware
Health API returns the data in the exhibit (only a portion is shown). If this JSON is converted to a
Python dictionary and assigned to the variable “d”, how the status is accessed that is indicated on
line 16?
Cisco SD-WAN deployment must be troubleshooted using vManage APIs. A call to vEdge Hardware
Health API returns the data in the exhibit (only a portion is shown). If this JSON is converted to a
Python dictionary and assigned to the variable “d”, how the status is accessed that is indicated on
line 16?Options
Discussion
Its D, most official SD-WAN API labs and the exam blueprints show similar Python access patterns.
B tbh, since if the JSON keys 'data' and 'statusList' are objects and not lists, you wouldn't need index positions. Sometimes these API outputs skip nesting with arrays if there’s only one element. I might be off if they’re always arrays here, though. Anyone else see examples where it's not a list?
B feels right if 'data' and 'statusList' are dicts, but I'm not totally sure. D might fit too.
Option B looks right to me if both 'data' and 'statusList' are dicts, which happens sometimes in Cisco API examples. The trap is with D if you're not sure they're lists. Maybe I'm missing a detail from the exhibit, though.
B , saw something similar in an official practice test and the dict style was shown there.
If statusList isn't a list, B.
B tbh, since if 'data' and 'statusList' are dictionaries (not lists), that's the syntax. I could be missing something with the array structure but that's my read.
D. you need to use both string keys and integer indices when you have lists like this in nested JSON.
Makes sense from the JSON structure, you need to index into the lists using [0] and use string keys for the dictionaries. D is correct here, pretty sure that's also what shows up in similar practice questions.
B . Feels like a common trap if you miss that 'data' and 'statusList' could be dicts, not lists.
Be respectful. No spam.