Exam 200-901 topic 1 question 77 discussion

B and C.

B&C are the correct answers. Take a look at the DevNet programmability basic videos, https://developer.cisco.com/video/net-prog-basics/ There are 3 main functions that meraki API provides: Dashboard API, Scanning API and Captive Portal API

C, E We all know that you can configure network devices via the Dashboard API See link below on how to configure streaming from a Meraki Camera: https://documentation.meraki.com/MV/Advanced_Configuration/External_RTSP

C and E

B, C, and E are all plausible. But the "mobile apps" part of B makes no sense. A captive portal would open a browser when you try to connect, so unless your mobile app has a browser integrated, that's nonsense. C and E don't require leaps in logic, so that's what I'm going with.

Configuring network devices via the Dashboard API: The Dashboard API allows developers to programmatically configure and manage network devices, such as switches, routers, and wireless access points. Retrieving live streams from a Meraki Camera: The Meraki Camera API allows developers to retrieve live video streams from Meraki cameras, as well as access historical video footage and metadata.

Tricky question, although I'd vote for B+C

B and C from Section 7.5 of the official Cisco course in Learning Library

this question is terrible. but that's what you get when a non meraki person writes the exam. a - is for sure not correct. there's no LoRaWAN in meraki. b - poorly worded. does this mean the built in captive portal in dashboard? does it mean excap? and i'd think this should say mobile devices not apps. and yes, meraki api does allow for configuration of the splash page. so, it seems this one could also be true. c - this one is for sure correct d - POST/networks/{networkId}/sm/devices/{deviceId}/installApps part of systems manager. so this one is correct. e - GET/devices/{serial}/camera/videoLink used without a timestamp will generate a link to live video in dashboard. so, for me this one is also correct. has nothing to do with rtsp.

Answer B&C The Meraki enterprise cloud-managed networking infrastructure service has five different APIs for integration. They are the: Dashboard API, a RESTful service for device provisioning, management, and monitoring. Webhook API, a real-time notification system for network alerts, covering events and network health Location Streaming API, an HTTP POST method providing Wi-Fi and Bluetooth client location information (GPS, X/Y) based on Meraki Access Point (AP) map placement, and client signal strength. External Captive Portal (EXCAP) API, enabling an organization to build out custom engagement models at Wi-Fi access points. MV Sense API, a combination of REST APIs and realtime MQTT stream supporting oversight of a physical space.

B and C https://developer.cisco.com/meraki/ According to the link, I think that even E could be a correct answer

C & E: "Through both REST and MQTT API endpoints, request or subscribe to historical, current, or real-time data generated in the camera to feed into your application and start using your camera for more than just security." Captive portal is used to connect your webserver (where the splash page is hosted) and the Access Point, so that when people connect to your public WiFi they are redirected to that webserver page, I do not see how a mobile app can use the API to integrate that service tbh, and even if that was doable, why only mobile apps?

I would say B and C. E is actually pretty new and I am not sure about it. Back in the days, you were able to get just a snapshot of the cammera, not the RSTP stream.

B and C https://developer.cisco.com/meraki/captive-portal-api/#!overview/introduction-to-captive-portal-api

It looks like be more B and C: The Meraki enterprise cloud-managed networking infrastructure service has five different APIs for integration. They are the: • Dashboard API, a RESTful service for device provisioning, management, and monitoring. • Webhook API, a real-time notification system for network alerts, covering events and network health • Location Streaming API, an HTTP POST method providing Wi-Fi and Bluetooth client location information (GPS, X/Y) based on Meraki Access Point (AP) map placement, and client signal strength. • External Captive Portal (EXCAP) API, enabling an organization to build out custom engagement models at Wi-Fi access points. • MV Sense API, a combination of REST APIs and realtime MQTT stream supporting oversight of a physical space.

The Cisco Meraki Dashboard API is an interface for software to interact directly with the Meraki cloud platform and Meraki managed devices. The API contains a set of tools that are known as endpoints for building software and applications that communicate with the Meraki Dashboard for use cases such as provisioning, bulk configuration changes, monitoring, and role-based access controls. The Dashboard API is a modern, RESTful API using HTTPS requests to a URL and JSON as a human-readable format. The Dashboard API is an open-ended tool can be used for many purposes. Here are some examples of how it is used today by Meraki customers: Add new organizations, administrators, networks, devices, VLANs, and Service Set Identifiers (SSIDs). Provision thousands of new sites in minutes with an automation script. Automatically onboard and off-board teleworker devices for new employees. Build your own dashboard for store managers, field technicians, or unique use cases.

You can't watch the live stream from the API, you can back a link to the live stream. I'm not sure with this question but I will go with Captive and device Configuration