Evolving Technologies and the CCIE. Meat and jam.

I recently read an interesting article by Terry Jenkins (from NC-Expert) on why the Evolving Technologies section of the CCIE written is failing everyone. While it should be kept in mind that Terry has a goal, which is to bring more people to their training courses, what he says in the article is very true.

The Evolving Technologies (ET) section was brought into the CCIE written exams recently and will be added to all tracks, eventually.

The question is, should it?

I will highlight some of the salient points from Terry’s article here, but please do read the full article.

Is it just a marketing ploy?

Is the ET section a marketing ploy, as Terry suggests? Not many people studying for the CCIE have a need to study anything to do with the Internet of Things. However, more services are becoming cloud-based. SaaS is extremely popular and will continue to be so. Software Defined Networking is becoming more prevalent as Cisco upgrades their product lines to support REST and Python APIs.

But this is not a one-size fits all scenario. Whilst the chances of a CCIE in Routing and Switching may never touch anything IoT, there are business drivers that may embrace the cloud, as well as tools to make their life easier, which would be SDN.

But what of the other areas?

Breaking down the Evolving Technologies sections

Let’s break down the ET sections.

6.1 Cloud

The cloud is big, cost effective and offloads many worries, such as business continuity, to third parties.

But, how much is relevant to the CCIE? Let’s look through the topics:

6.1.a Compare and contrast cloud deployment models
6.1.a.1 Infrastructure, platform, and software services (XaaS)
6.1.a.2 Performance and reliability
6.1.a.3 Security and privacy
6.1.a.4 Scalability and interoperability
6.1.b Describe cloud implementations and operations
6.1.b.1 Automation and orchestration
6.1.b.2 Workload mobility
6.1.b.3 Troubleshooting and management
6.1.b.4 OpenStack components

These are only relevant if you are running your own cloud. If you outsource you email to Office 365 then this bears no relevance to the role of the network engineer. If you are running your own cloud, then this will be relevant.

6.2 Network Programmability (SDN)

6.2.a Describe functional elements of network programmability (SDN) and how they interact
6.2.a.1 Controllers
6.2.a.2 APIs
6.2.a.3 Scripting
6.2.a.4 Agents
6.2.a.5 Northbound vs. Southbound protocols
6.2.b Describe aspects of virtualization and automation in network environments
6.2.b.1 DevOps methodologies, tools, and workflows
6.2.b.2 Network/application function virtualization (NFV, AFV)
6.2.b.3 Service function chaining
6.2.b.4 Performance, availability, and scaling considerations

DevOps is quite fun, and learning Python will be a great help to the network engineer over the next few years. Cisco ASAs come with a REST API, the Nexus line can be programmed through Python. So having SDN within the CCIE does make a little sense.

6.3 Internet of Things (IoT)

6.3.a Describe architectural framework and deployment considerations for Internet of Things
6.3.a.1 Performance, reliability, and scalability
6.3.a.2 Mobility
6.3.a.3 Security and privacy
6.3.a.4 Standards and compliance
6.3.a.5 Migration
6.3.a.6 Environmental impacts on the network

Does the CCIE need to know how to get their refrigerator to talk to the toaster through OSPF? No. Do we need to know how to program Arduino boards? No. This is where the CCIE written exams become messy.

Meat and Jam

IoT does not belong on any of the existing CCIE exams, neither does knowing how to run your own cloud. SDN is more of a gray area. I can see why this could be relevant and this is where the written exams fall apart. It’s like ordering a great dinner and having it delivered with your desert. On the same plate.

Emerging Technologies CCIE trifle

The thing is, the Evolving Technologies section is here now. Until Cisco remove it from the existing CCIE written exams, we have to put up with it. Even if it does not belong. The CCIE student now has this added worry. Returning to Terry’s article he puts it very succinctly:

At this point his confidence is all but gone and it’s replaced with frustration and anger. He is telling himself I am going to fail this exam, not because I do not know collaboration but because I do not know technologies that have nothing to do with collaboration!

How can you prepare for Evolving Technologies?

You need to prepare for the new section. Even though it only accounts for 10% of the exam, this is 10% that you cannot afford to lose.

Embrace IoT

NC-Expert run a course, and at $399 is a good price for a one-day course. I am not affiliated with NC-expert in any way, nor do I have any experience of their courses, but they are a Cisco Learning partner.  If courses are not your thing, then there are books that can help.


Virtual Routing in the Cloud

Virtual Routing in the Cloud
Under 300 pages long, this covers a large section of the Cloud part of the ET. It does seem a little light in places, though. But would serve as a good introduction.

Cloud Computing: Automating the Virtualized Data Center

Cloud Computing: Automating the Virtualized Data Center
Slightly heavier than Virtual Routing in the Cloud, this book seems to be more concerned with the business-side of things, such as ITIL, and Service Delivery.

The Policy Driven Data Center with ACI: Architecture, Concepts, and Methodology

The Policy Driven Data Center with ACI: Architecture, Concepts, and Methodology
This is a good book. I bought it a few months ago and it makes for good reading. It kind of bridges the Cloud section to the Network Programmability (SDN) section, and covers  OpenStack, REST and Python in good depth.

Network Programmability (SDN)

As well as the Policy Driven Data Center book above, there are other books on SDN.

Programming and Automating Cisco Networks: A Guide to Network Programmability and Automation in the Data Center, Campus, and WAN

Programming and Automating Cisco Networks: A Guide to Network Programmability and Automation in the Data Center, Campus, and WAN
This covers a lot of Python, Bash scripting, NX-OS, and APIC-EM (Application Policy Infrastructure Controller Enterprise Module).

Internet of Things (IoT)

IoT Fundamentals: Networking Technologies, Protocols, and Use Cases for the Internet of Things

IoT Fundamentals: Networking Technologies, Protocols, and Use Cases for the Internet of Things
Although not yet released, this is a fundamentals book and should be a good introduction.

Internet of Things / Internet of Everything: A Practical Architectural Approach

This book (again a Fundamentals book and not yet released) seems closer aligned to the topics on the CCIE Written, covering architecture, scalability, security, and standards. I would probably buy this book instead of the one above.

End Note

There are a few books that can help us get through the new Evolving Technologies section. Like it or not, this is something we will have to put up with until Cisco decide otherwise. We may not agree with the change in the CCIE, but with a little reading, it is a section that can be passed.


  1. Marcus Castilho October 25, 2016
    • Stuart Fordham October 25, 2016