Automation & APIs

Covers Lesson 1 and Lesson 2

Checks that you can say precisely what a controller does and does not take over, and that you can read an API call and its JSON payload accurately.

Topics covered

• Configuration drift and intended state
• What a controller centralises and what it does not
• The three planes
• Verbs to CRUD and status codes
• JSON syntax and structure

Every question here is answerable from the first-party notes of the lessons above. You commit to an answer before you see whether it was right.

This quiz is a Week 9 milestone in its own right. Passing it does not change the completion state of any individual lesson, and you do not need it to finish the lessons it covers.

Section quiz

Automation & APIs

8 questions covering Lesson 1 and Lesson 2. Answer each one before you see whether you were right.

Question 1 of 8

1. In controller-based networking, what does the controller centralize?

2. What problem does keeping the intended configuration in version control solve that per-device CLI does not?

3. Which planes do automation and controllers operate in?

4. What is the characteristic risk of network automation, and what mitigates it?

5. Which HTTP verb reads data without changing it, and which CRUD operation is POST?

6. A response comes back 401. What went wrong, and whose problem is it?

7. Which of these breaks JSON validity?

8. A controller returns many interfaces rather than one. Which structure wraps them, and what separates each object?

Back to Lesson 2 Continue to Lesson 3

Back to Week 9