Appendix
Answers to Review Questions
Chapter 1
1. a. Explanation: Processing should occur as close to the source of the data (sensor/thing) as possible. If an edge node can perform the computation, it should be used first.
2. a. Explanation: IoT compute processing can be staged in a hierarchical fashion. An edge node can send data to a fog node, and a fog node can send data to another fog node or toward a data center or cloud provider.
3. a. Explanation: IoT networks are more complex because they have a larger scale and more attack vectors than traditional IT networks.
4. b. Explanation: Availability is the most significant factor due to financial impacts to the business.
5. b. Explanation: OT networks connect to robots, power grids, refineries, and other markets where a compromise could result in the loss of life. Therefore, security must be considered to prevent malicious attackers from causing personal injury.
Chapter 2
1. c. Explanation: NIST only provides definitions for SaaS, PaaS, and IaaS.
2. a. Explanation: CCC’s application models support a mixture of customized services, images, and containers.
3. b. Explanation: Network Functions Virtualization (NFV) is an architectural framework, whereas VNF is the software version of an NF (that is, a virtual load balancer).
4. a. Explanation: Rehosting (aka lift-and-shift) involves redeploying applications to an IaaS or Bare Metal as-a-service (BMaaS) environment without making any changes to the applications.
5. d. Explanation: vAnalytics is an optional analytics and assurance service that includes many advanced monitoring capabilities.
Chapter 3
1. b. Explanation: Configuring a large number of devices via the CLI is not only time consuming, it also leads to an increase in human error, ultimately putting the business at risk.
2. d. Explanation: To authenticate to Cisco’s DNA Center Controller, a POST operation must be used. This is because we are sending the login credentials to the controller to be verified.
3. b. Explanation: CRUD stands for CREATE, READ, UPDATE, and DELETE. These are the common actions associated with the manipulation of data. For example, a database uses these actions.
4. a and b. Explanation: Postman and Ansible both have the ability to specify a RESTful API or URL to be used to practice or test API functions. Telnet and SSH are transport methods, whereas XML and JSON are data structures.
5. a. Explanation: A JSON data format is built from key-value pairs. For example, “user”: “Jason” is a key value pair, where user is the key and Jason is the value.
6. c. Explanation: An HTTP status code of 401 is for Unauthorized, meaning incorrect login credentials or not having valid authentication to a destination. See the following table for more HTTP Response codes.
HTTP Status Code |
Result |
Common Reason for Response Code |
200 |
OK |
Using a GET or POST to exchange data with an API. |
201 |
Created |
Creating resources via a REST API call. |
400 |
Bad Request |
Request failed because of a client-side issue. |
401 |
Unauthorized |
Client not authenticated to access site or API call. |
403 |
Forbidden |
Access not granted based on supplied credentials. |
404 |
Not Found |
Page at HTTP URL location does not exist or is hidden. |
7. a, b, and c. Explanation: Source Control Management can help with many different aspects of software delivery. The most common are code revisions, associated developers, sharing of code, and becoming more agile in the development process. Real-time telemetry of the software database and automatic blocking of malicious code have nothing to do with SCM.
8. b. Explanation: PPDIOO consists of six components: Prepare, Plan, Design, Implement, Operate, and Optimize. Please refer to Figure 3-29 for more information.
9. b. Explanation: Ansible uses Yet Another Markup Language (YAML) for the creation of Playbook files. TAML doesn’t exist.
10. a. Explanation: ansible-playbook <filename.yaml> is the correct command to execute a Playbook. Playbooks are built from Yet Another Markup Language (YAML) files. TAML files do not exist.