WEBVTT

0:00:09.660000 --> 0:00:14.140000
 Hello and welcome to this video, part
 of this CCNA Exam Assessment Series,

0:00:14.140000 --> 0:00:17.540000
 where we're going to be assessing you
 on your knowledge of virtualization

0:00:17.540000 --> 0:00:25.080000
 fundamentals. Question 1.

0:00:25.080000 --> 0:00:29.080000
 When purchasing a server, which of the
 following elements are typically

0:00:29.080000 --> 0:00:39.300000
 not included? And that
 would be the KVM.

0:00:39.300000 --> 0:00:44.160000
 Remember in this particular context,
 KVM stands for keyboard, video, and

0:00:44.160000 --> 0:00:47.720000
 mouse. So when you purchase a server,
 it typically does not come with

0:00:47.720000 --> 0:00:56.940000
 a keyboard, a monitor, or a
 video monitor, or a mouse.

0:00:56.940000 --> 0:01:06.100000
 Question 2. At its most basic level, which
 of the following answers provides

0:01:06.100000 --> 0:01:12.980000
 a definition of a virtual machine?


0:01:12.980000 --> 0:01:18.720000
 The correct answer here is answer A,
 a single physical server running

0:01:18.720000 --> 0:01:22.040000
 two or more operating systems.

0:01:22.040000 --> 0:01:36.940000
 Question 3. Which software slash hardware
 element is critical for determining

0:01:36.940000 --> 0:01:46.540000
 the quantity of VCPUs a
 single server supports?

0:01:46.540000 --> 0:01:52.340000
 The correct answer is the total quantity
 of simultaneous threads that

0:01:52.340000 --> 0:01:59.580000
 can be processed.

0:01:59.580000 --> 0:02:09.760000
 Question 4. Matts of following terms
 related to virtualization with their

0:02:09.760000 --> 0:02:19.100000
 definitions. And here you can see how
 those terms are correctly paired

0:02:19.100000 --> 0:02:26.320000
 up with the correct definitions.

0:02:26.320000 --> 0:02:43.780000
 Question 5. Which of the following
 are examples of hypervisors?

0:02:43.780000 --> 0:02:46.740000
 And all of these answers
 are correct.

0:02:46.740000 --> 0:02:54.680000
 A through D are all examples of
 different types of hypervisors.

0:02:54.680000 --> 0:03:05.860000
 Question 6. In the diagram below showing
 the interconnections between

0:03:05.860000 --> 0:03:10.880000
 servers in a data center, identify the
 correct acronyms for the devices

0:03:10.880000 --> 0:03:14.600000
 represented as X and Y.

0:03:14.600000 --> 0:03:19.780000
 So once again, what's the correct acronym
 for all these X devices right

0:03:19.780000 --> 0:03:28.840000
 here? And what's the correct acronym
 for these guys right there?

0:03:28.840000 --> 0:03:34.340000
 And here are the answers.

0:03:34.340000 --> 0:03:40.840000
 Those X devices are top of rack or
 TOR switches top of rack and the Y

0:03:40.840000 --> 0:03:48.240000
 devices are end of rack
 switches or EOR.

0:03:48.240000 --> 0:03:58.920000
 Question 7. Which of the following are
 typically options that you'd have

0:03:58.920000 --> 0:04:02.500000
 to select before creating
 a virtual machine?

0:04:02.500000 --> 0:04:08.860000
 Select two answers.

0:04:08.860000 --> 0:04:13.400000
 So you would typically have to select
 your quantity of virtual CPUs for

0:04:13.400000 --> 0:04:17.260000
 each virtual machine and the amount
 of RAM that that virtual machine was

0:04:17.260000 --> 0:04:20.600000
 going to be needing.

0:04:20.600000 --> 0:04:31.560000
 Question 8. Which of the following
 is a product offering by Cisco that

0:04:31.560000 --> 0:04:35.840000
 can be used in place of a virtual switch
 that may come bundled with a

0:04:35.840000 --> 0:04:39.940000
 hypervisor? In other words, a lot of hypervisors
 from your previous question

0:04:39.940000 --> 0:04:46.300000
 you saw come with a pre-installed
 or pre-default virtual switch.

0:04:46.300000 --> 0:04:49.900000
 But Cisco actually sells a product
 that you can use their product as a

0:04:49.900000 --> 0:04:53.280000
 virtual switch which will give you
 more benefits and features than the

0:04:53.280000 --> 0:04:57.560000
 default virtual switch that might come
 pre-installed with a hypervisor.

0:04:57.560000 --> 0:05:01.220000
 So which one of these is Cisco's
 product that does that?

0:05:01.220000 --> 0:05:12.200000
 And that would be
 the Nexus 1000 V.

0:05:12.200000 --> 0:05:22.020000
 Question 9. Which of the following
 resources are commonly virtualized

0:05:22.020000 --> 0:05:26.220000
 so that they can be shared among many
 virtual machines running within

0:05:26.220000 --> 0:05:28.780000
 a single host server?

0:05:28.780000 --> 0:05:31.940000
 Select three answers.

0:05:31.940000 --> 0:05:40.260000
 So when you have a physical server
 and you want to divide that up into

0:05:40.260000 --> 0:05:45.140000
 multiple virtual machines, typically
 the physical NIC is virtualized so

0:05:45.140000 --> 0:05:48.420000
 that each virtual machine can
 have its own virtual NIC.

0:05:48.420000 --> 0:05:52.080000
 The physical RAM memory is virtualized
 so each virtual machine can have

0:05:52.080000 --> 0:05:54.240000
 some dedicated memory.

0:05:54.240000 --> 0:06:01.460000
 And the physical CPU is virtualized
 into virtual CPUs.

0:06:01.460000 --> 0:06:12.380000
 Question 10. When using containerization
 in order to make an application

0:06:12.380000 --> 0:06:17.540000
 more portable, what components would
 you typically expect to find within

0:06:17.540000 --> 0:06:22.460000
 the container? Select
 three answers.

0:06:22.460000 --> 0:06:29.960000
 Well, you'd expect to find an operating
 system or at least a stripped

0:06:29.960000 --> 0:06:32.520000
 down version of an
 operating system.

0:06:32.520000 --> 0:06:35.980000
 You'd expect to find some application
 code in whatever libraries were

0:06:35.980000 --> 0:06:41.920000
 associated with that
 application code.

0:06:41.920000 --> 0:06:51.860000
 Question 11. Which of the following
 comparisons between containers and

0:06:51.860000 --> 0:06:54.880000
 virtual machines or VMs is true?

0:06:54.880000 --> 0:06:59.780000
 Select two answers.

0:06:59.780000 --> 0:07:05.540000
 The correct answers are A, containers
 are typically smaller in size than

0:07:05.540000 --> 0:07:11.040000
 virtual machines, and D, virtual machines
 are primarily designed to virtualize

0:07:11.040000 --> 0:07:18.580000
 hardware so that multiple operating systems
 can be run on a single machine.

0:07:18.580000 --> 0:07:30.420000
 Question 12. A what, a fill in the
 blank, might be taken of a virtual

0:07:30.420000 --> 0:07:36.180000
 machine to preserve and record its operational
 state in time so that it

0:07:36.180000 --> 0:07:44.320000
 can be reverted back to
 that state later on.

0:07:44.320000 --> 0:07:51.860000
 Question 13. Of these answers, the
 correct answer was a snapshot.

0:07:51.860000 --> 0:08:03.100000
 Question 13. Which type of hypervisor
 is also called a native or bare

0:08:03.100000 --> 0:08:05.700000
 metal hypervisor?

0:08:05.700000 --> 0:08:20.300000
 And that would be a
 type 1 hypervisor.

0:08:20.300000 --> 0:08:29.860000
 Question 14. Customer A, customer B, and
 customer C all have devices connected

0:08:29.860000 --> 0:08:35.940000
 to Router X. Given this situation, what
 benefits may be obtained by implementing

0:08:35.940000 --> 0:08:43.040000
 VRFs on this Router?

0:08:43.040000 --> 0:08:46.880000
 Well, VRFs will allow you to keep customer
 traffic isolated from each

0:08:46.880000 --> 0:08:49.740000
 other. That is the correct answer.


0:08:49.740000 --> 0:08:54.280000
 VRFs do not have anything to do with
 encryption, and they do not enhance

0:08:54.280000 --> 0:08:57.800000
 or make routing more efficient, and
 they certainly don't have anything

0:08:57.800000 --> 0:09:01.520000
 to do with sharing QS policies
 between customers.

0:09:01.520000 --> 0:09:05.560000
 Answer C was the only
 correct answer.

0:09:05.560000 --> 0:09:18.000000
 Question 15. Which of the following
 are examples of type 2 hypervisors?

0:09:18.000000 --> 0:09:20.640000
 Select two answers.

0:09:20.640000 --> 0:09:30.660000
 The correct answers are B, Virtual
 Box, and D, VMware, Vorkstation.

0:09:30.660000 --> 0:09:35.480000
 Remember that a type 2 hypervisor is
 a type of hypervisor that you install

0:09:35.480000 --> 0:09:38.880000
 on top of an existing
 operating system.

0:09:38.880000 --> 0:09:42.740000
 So if you have Microsoft Windows, for
 example, as your operating system,

0:09:42.740000 --> 0:09:48.080000
 you have to find a type 2 hypervisor
 that is compatible with Microsoft

0:09:48.080000 --> 0:09:52.080000
 Windows, like Virtual Box
 or VMware Workstation.

0:09:52.080000 --> 0:09:56.280000
 Whereas if you have Mac OS, for example,
 which is running Linux under

0:09:56.280000 --> 0:09:59.640000
 the hood, you might have to find a
 different type of type 2 hypervisor

0:09:59.640000 --> 0:10:03.960000
 like VMware Fusion or something
 to run on that.

0:10:03.960000 --> 0:10:08.520000
 But type 2 hypervisors require some underlying
 operating system to already

0:10:08.520000 --> 0:10:20.700000
 be in place. Question 16.

0:10:20.700000 --> 0:10:24.960000
 Given the following diagram, when a
 routing update arrives on interface

0:10:24.960000 --> 0:10:30.220000
 1 of the router, notice that it's router
 B in the middle, which of the

0:10:30.220000 --> 0:10:33.500000
 following answers will be true?

0:10:33.500000 --> 0:10:37.320000
 So notice the router A is sending a
 routing update to router B, and it

0:10:37.320000 --> 0:10:40.900000
 is arriving on interface
 1 of router B.

0:10:40.900000 --> 0:10:50.980000
 Alright the correct answer is the update
 will be processed, but not forwarded.

0:10:50.980000 --> 0:10:54.540000
 And that's because router B has each
 one of its interfaces in different

0:10:54.540000 --> 0:10:56.900000
 and unique VRFs.

0:10:56.900000 --> 0:11:01.520000
 When a routing update arrives on an
 interface that's in a VRF, that VRF

0:11:01.520000 --> 0:11:06.720000
 and any other interfaces in that particular
 VRF can process it, but the

0:11:06.720000 --> 0:11:10.040000
 whole point of VRFs is to
 keep things separate.

0:11:10.040000 --> 0:11:14.000000
 So anything that arrives on interface 1
 will not be allowed to go to interface

0:11:14.000000 --> 0:11:18.960000
 2 or 3 because those are in their own
 completely separate virtual routing

0:11:18.960000 --> 0:11:21.160000
 and forwarding instances.

0:11:21.160000 --> 0:11:28.060000
 And that concludes this video for
 this portion of the assessment.

0:11:28.060000 --> 0:11:29.900000
 Thank you for watching and
 I hope it was helpful.