Join Telegram Study Group ▷
On Cisco Live US 2019, Cisco announced several major changes to all certification tracks from CCNA to CCIE. How does this affect candidates who are currently studying for CCIE RS Certification? We will answer this question and provide you with a clear way to learn.
What's In a Name
First, our favorite CCIE track is being renamed to route and exchange from CCIE to the CCIE enterprise infrastructure. This is just a name change that does not affect anything other than our logo. This change will take place on February 24, 2023.
To the Test
The next change that Cisco is implementing will be the exam. There will be no difference between the CCIE R / S qualification (R / S written exam) and CCNP Core exam. Specifically, 300 / 401 ENCOR "implementing and operating Cisco Enterprise Network Core Technologies" is now qualified to do one of the following three things:
Taking the CCNP professional exam becomes a CCNP enterprise to take the CCIE Enterprise Infrastructure experiment exam, become the CCIE Enterprise Infrastructure to take the CCIE Enterprise Wireless Lab exam, and become CCIE Enterprise Wireless although Wireless is included in these changes, we will focus on wireless development in another blog post. Pay attention to it.
In addition to the subject change (we will discuss), the new laboratory has a major format change in addition to the CCIE laboratory exam. The experimental exam is now divided into two modules, instead of the previous R / S three modules. In the first 3-hour module, candidates need to create, analyze, validate, and optimize network design. They must also translate customer requirements into solutions and assess network preparedness to support these proposed solutions. In the second module (5 hours long), the candidate will use a combination of virtual devices, physical devices and Web-based projects to build the network according to design requirements, customer requirements and restrictions (and other expectations).
In terms of technologies, there are significant additions to the CCIE Routing & Switching Lab Exam (again, soon-to-be-called the CCIE Enterprise Infrastructure Exam), such as:
2. Software Defined Infrastructure (25%)
2.1 Cisco SD Access
2.1.a Design a Cisco SD Access Solution
2.1.a I Underlay Network (ISIS, manual/PnP)
2.1.a ii Overlay Fabric Design (LISP, VXLAN, Cisco TrustSec)
2.1.a iii Fabric Domains (single-site and multi-site)
2.1.b Cisco SD Access Deployment
2.1.b I Cisco DNA Center Device Discovery and Device Management
2.1.b ii Add Edge Node Devices to an Existing Fabric
2.1.b iii Host On-boarding (wired endpoints only)
2.1.b iv Fabric Border Handoff
2.1.c Segmentation
2.1.c I Macro-level Segmentation using VNs
2.1.c ii Micro-level Segmentation using SGTs (using Cisco ISE)
2.1.d Assurance
2.1.d I Network and Client Health (360)
2.1.d ii Monitor and Troubleshooting
More information on SD-Access can be found here.
2.2 Cisco SD-WAN
2.2.a Design a Cisco SD-WAN Solution
2.2.a I Orchestration Plane (vBond, NAT)
2.2.a ii Management Plane (vManage)
2.2.a iii Control Plane (vSmart, OMP)
2.2.a iv Data Plane (vEdge/cEdge)
2.2.b WAN Edge Deployment
2.2.b I On-boarding New Edge Routers
2.2.b ii Orchestration with Zero-touch Provisioning/Plug-And-Play
2.2.b iii OMP
2.2.b iv TLOC
2.2.c Configuration Templates
2.2.d Localized Policies (only QoS)
2.2.e Centralized Policies
2.2.e I Application Aware Routing
2.2.e ii Topologies
More information on SD-WAN can be found here.
5. Infrastructure Automation and Programmability (15%)
5.1 Data Encoding Formats
5.1.a JSON
5.1.b XML
5.2 Automation and Scripting
5.2.a EEM Applets
5.2.b Guest Shell
5.2.b I Linux Environment
5.2.b ii CLI Python Module
5.2.b iii EEM Python Module
5.3 Programmability
5.3.a Interaction with vManage API
5.3.a I Python Requests Library or Postman
5.3.a ii Monitoring Endpoints
5.3.a iii Configuration Endpoints
5.3.b Interaction with Cisco DNA Center API
5.3.b I HTTP Request (GET, PUT, POST) via Python Requests Library or Postman
5.3.c Interaction with Cisco IOS XE API
5.3.c I Via NETCONF/YANG using Python ncclient Library
5.3.c ii Via RESTCONF/YANG using Python Requests Library or Postman
5.3.d Deploy and Verify Model-driven Telemetry
5.3.d I Configure On-change Subscription using gRPC
Staying Ahead of the Game
SPOTO will be updating our blog frequently to share more information about these and other changes announced at Cisco Live. Leave any questions you may have in the Comments section below and/or let us know what specific changes you're interested in knowing even more about. We are already busy sorting out the content to guide you through Cisco undefined new requirements and updates. We will release our game plan as soon as we are finished.
