A collection of guided practice labs and solutions for the Cisco 350-401 ENCOR v1.1 exam.

• Cisco ENCOR v1.1 Practice Labs
  • About the Exam
  • About the Practice Labs
  • How to Use
  • Saving and Restarting Lab Progress

According to Cisco's official certification listing,

(ENCOR 350-401) is a 120-minute exam associated with the CCNP and CCIE Enterprise Certifications. This exam tests a candidate's knowledge of implementing core enterprise network technologies, including dual stack (IPv4 and IPv6) architecture, virtualization, infrastructure, network assurance, security, and automation.

The exam itself consists of multiple choice, drag & drop, and hands-on lab questions. It will behoove you to read the exam topics closely to get a sense of the level of depth required for each topic.

Tip: Verbs matter!

Topics starting with Configure, Troubleshoot, or Verify are likely to require configuration-level knowledge, whereas Explain, for instance, is more likely to appear as a multiple choice or drag & drop question.

Keep in mind that while some topics may not show up as labs, you may still encounter configuration files or show commands as part of a multiple choice question. That is to say, as much as possible... lab, lab, lab!

Each exam topic has:

• A respective Lab folder with:

  • A .yaml file for importing the starting configuration into CML.
  • A .md file with instructions for completing the lab.

• A respective Solution folder with:

  • A .yaml file representing a correctly configured lab state. (auto-grader work in progress!)
  • A .md file with answers to the lab instructions.

These labs are built for Cisco CML v2.6 and assume you have a running instance. This is not a trivial assumption, but if you don't have a local instance, consider reserving a free CML instance (as well as many other Cisco solutions) on Cisco's DevNet Sandbox!

git clone https://github.com/neythonstreitz/encor-problem-sets.git

Alternatively, you can view the instructions from the Github website and download individual lab .yaml files. Only the .yaml file is necessary for the lab to load in CML, so locally cloning the repo is not required (for now).

Get some coffee... this step may take a few minutes...

The device console should appear at the bottom of the screen.

If you plan on spinning down your CML topology (or are using a reserved sandbox), make sure to follow these steps to preserve your progress:

1. Copy the running configuration of all devices to their startup configuration
   • Ex: R1# copy run start
2. Under the NODES panel, select all nodes and EXTRACT CONFIGS
   • This will pull the configs. from the devices and save them to the lab .yaml file
3. Under the LAB tab, select Download Lab
   • A lab.yaml file should download to your computer.
4. When importing the in-progress lab, remember to use your downloaded .yaml file (not the one from this repo)
   • Make sure to write down where you stopped so you can pick back up seamlessly!

Need to start a lab over? If you have NOT saved your progress (as shown above) you can simply restart all the nodes:

• Under LAB -> Select Stop Lab -> Wait for nodes to stop -> Select Start Lab

Alternatively, if you have modified the startup configs of any of your devices, the nodes will use the modified startup config instead of the original pre-configured startup. In that case, simply delete the current lab and re-import a fresh lab .yaml file from this repo.