300-435 — frequently asked questions

The -b flag tells Git to create a new branch before checking it out, combining two steps into one command.

Yes, use 'git branch <name>' to create it, then 'git checkout <name>' to switch later.

POST allows sending larger payloads and triggers actions or creates new resources, whereas GET is for retrieving data and has length limits.

While some older or custom integrations might handle XML, the standard and documented payload format for DNA Center webhooks is JSON.

Webhooks are push notifications sent from a source (Meraki) to a destination. POST is used because it allows sending a payload of data (the alert details) in the request body.

It is a decorator that maps a specific URL path to a function that handles incoming POST requests, making the function act as a webhook receiver.

The organizationId is a path parameter defined in the URL (/organizations/{organizationId}/networks). Including it in the body is redundant and often causes validation failures in Meraki's API.

A POST request is used to create new resources. GET retrieves data, PUT updates existing resources, and DELETE removes them.

No, NETCONF (RFC 6241) strictly uses XML for all data exchange. JSON is not part of the NETCONF protocol specification.

JSON makes RESTCONF easier to use with modern web technologies and JavaScript libraries compared to the verbose XML used in NETCONF.