Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 200-901 Topic 4 Question 96 Discussion

Actual exam question for Cisco's 200-901 exam
Question #: 96
Topic #: 4
[All 200-901 Questions]

An engineer is creating an API to automatically obtain specific zones from Cisco Meraki MV cameras. The data that is provided when the API runs must represent the current analytic zones that are configured on the cameras. The API must start automatically at 6 p.m. every day and save the data on a server for further processing. Which part of the HTTP request must be configured to meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

When creating an API to interact with Cisco Meraki MV cameras, the request header must specify the correct content type to ensure the server understands the format of the request data. Setting the Content-Type header to 'application/json' indicates that the request body is formatted as JSON. This is essential for APIs that expect JSON data for requests and responses.

Additionally, the API must be scheduled to run automatically at 6 p.m. every day. This can be achieved using a cron job or a scheduling tool like cron in Unix-based systems or Task Scheduler in Windows.


Cisco DevNet Associate Certification Guide

Cisco Meraki API Documentation

Contribute your Thoughts:

Kris
9 days ago
Ah, the classic 'use XML when JSON is clearly the better option' scenario. Easy choice, team B!
upvoted 0 times
...
An
10 days ago
Haha, 'Content-Encoding set to application/xml'? What is this, the 90s? B is the way to go, no doubt.
upvoted 0 times
...
Lezlie
12 days ago
I believe the correct answer is B) request header with Content-Type set to 'application/json' because it specifies the format of the data being sent in the request.
upvoted 0 times
...
Torie
12 days ago
I'm with the others on this one. B is the clear choice here. Who would even think of using a redirect status code for this?
upvoted 0 times
...
Bernardine
13 days ago
I'm not sure, but I think D) request body with Content-Type set to 'application/xml' could also be a valid option.
upvoted 0 times
...
Elden
17 days ago
I agree with Ona, setting the Content-Type to 'application/json' makes sense for the API to work properly.
upvoted 0 times
...
Ona
18 days ago
I think the answer is B) request header with Content-Type set to 'application/json'.
upvoted 0 times
...
Gerald
23 days ago
Wait, why would we need to set the Content-Encoding header to XML? That doesn't make sense. Definitely option B.
upvoted 0 times
Donte
4 days ago
I agree, setting the Content-Type header to application/json makes more sense for this API.
upvoted 0 times
...
Meghan
6 days ago
Setting the Content-Encoding header to XML would not be suitable for this scenario. Option B is the way to go.
upvoted 0 times
...
Leonardo
15 days ago
Yeah, that's correct. It's important to specify the correct data format in the request header.
upvoted 0 times
...
Dong
20 days ago
I agree, setting the Content-Type header to application/json makes more sense for this API.
upvoted 0 times
...
...
Diane
1 months ago
Hmm, 302 is a redirect status code, so that doesn't seem right for this use case. I'd say B is the way to go.
upvoted 0 times
...
Jerry
1 months ago
The API needs to get the current analytic zones, so the response should be in JSON format, not XML. I'd go with option B.
upvoted 0 times
Avery
13 hours ago
JSON is definitely the way to go for this API. It's more lightweight and easier to work with than XML.
upvoted 0 times
...
Carolann
16 days ago
Setting the Content-Type to 'application/json' in the request header will ensure the data is returned in the correct format.
upvoted 0 times
...
Yolando
23 days ago
I agree, option B is the correct choice. JSON format is more suitable for this type of data.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77