WEBVTT

0:00:09.540000 --> 0:00:14.560000
 Hello and welcome to the second video
 in our CCNA Exam Assessment Series

0:00:14.560000 --> 0:00:16.280000
 for Network Fundamentals.

0:00:16.280000 --> 0:00:21.420000
 This section is about network topology
 architectures and WANs.

0:00:21.420000 --> 0:00:26.440000
 Let's go ahead and jump
 into our first question.

0:00:26.440000 --> 0:00:32.800000
 In a three-tier campus land design,
 which category of switch forwards

0:00:32.800000 --> 0:00:36.160000
 traffic between user devices?

0:00:36.160000 --> 0:00:46.140000
 The correct answer are access
 switches, answer D.

0:00:46.140000 --> 0:00:51.080000
 Question number two.

0:00:51.080000 --> 0:00:54.100000
 Fill in the blanks in
 the sentence below.

0:00:54.100000 --> 0:00:59.900000
 A two-tier campus design typically
 implements a blank topology at the

0:00:59.900000 --> 0:01:10.360000
 access layer and a blank topology
 at the distribution layer.

0:01:10.360000 --> 0:01:13.160000
 The correct answer is answer A.

0:01:13.160000 --> 0:01:18.260000
 A star topology is implemented at the
 access layer with the switch forming

0:01:18.260000 --> 0:01:22.580000
 the central point of the star and the
 various endpoints connected to that

0:01:22.580000 --> 0:01:27.940000
 switch being the endpoints of the star
 and a partial mesh topology is

0:01:27.940000 --> 0:01:30.220000
 implemented at the
 distribution layer.

0:01:30.220000 --> 0:01:34.480000
 Partial mesh because the distribution
 layer switches do not all connect

0:01:34.480000 --> 0:01:38.820000
 to each other nor do they necessarily
 all connect to the access layer

0:01:38.820000 --> 0:01:47.780000
 switches. Question three.

0:01:47.780000 --> 0:01:52.740000
 Which of the following answers provides
 an alternative name for a collapsed

0:01:52.740000 --> 0:01:56.040000
 core campus network design?

0:01:56.040000 --> 0:02:01.540000
 The correct answer is A.

0:02:01.540000 --> 0:02:08.260000
 A collapsed core is also
 called a two-tier design.

0:02:08.260000 --> 0:02:18.480000
 Question four. What role of switch exists
 in a three-tier campus design

0:02:18.480000 --> 0:02:22.880000
 that does not exist in a
 two-tier campus design?

0:02:22.880000 --> 0:02:29.920000
 The correct answer
 is a core switch.

0:02:29.920000 --> 0:02:34.400000
 A core switch does not exist in a two
-tier campus design but it does exist

0:02:34.400000 --> 0:02:43.020000
 in a three-tier question five.

0:02:43.020000 --> 0:02:52.160000
 Match the two-tier topology designs
 with their correct definitions.

0:02:52.160000 --> 0:03:06.300000
 And here is the correct pairing of the
 design name with its definition.

0:03:06.300000 --> 0:03:16.060000
 Question six. Which of the following
 statements are true about spine and

0:03:16.060000 --> 0:03:19.340000
 leaf network topology designs?

0:03:19.340000 --> 0:03:26.520000
 And you must select three
 correct answers.

0:03:26.520000 --> 0:03:29.780000
 And here are your correct answers.


0:03:29.780000 --> 0:03:33.840000
 Each spine switch must connect
 every leaf switch.

0:03:33.840000 --> 0:03:43.580000
 So if we draw this out, if we have a
 couple of spine switches here, and

0:03:43.580000 --> 0:03:51.900000
 a few leaf switches down here, like this,
 with the leaf switches connected

0:03:51.900000 --> 0:03:53.740000
 to the endpoints.

0:03:53.740000 --> 0:03:57.080000
 So each spine switch must connect
 to every leaf switch.

0:03:57.080000 --> 0:04:02.160000
 So every leaf switch would have a connection
 to spine one and a connection

0:04:02.160000 --> 0:04:05.300000
 to spine two. That's requirement.

0:04:05.300000 --> 0:04:09.120000
 A spine switch must not connect
 to another spine switch.

0:04:09.120000 --> 0:04:12.260000
 So notice there's no connections
 here between the spine switches.

0:04:12.260000 --> 0:04:17.140000
 Now if this was a two-tier or a three
-tier network design, not spine leaf,

0:04:17.140000 --> 0:04:20.860000
 we would expect to find some sort
 of connection between these.

0:04:20.860000 --> 0:04:25.000000
 And endpoints connect
 only to leaf switches.

0:04:25.000000 --> 0:04:28.260000
 Your endpoints being your servers and your
 servers with your virtual machines

0:04:28.260000 --> 0:04:31.400000
 would only connect to the
 leaf switches down here.

0:04:31.400000 --> 0:04:38.520000
 You would never see them connecting
 to a spine switch.

0:04:38.520000 --> 0:04:43.220000
 Question number seven.

0:04:43.220000 --> 0:04:52.640000
 Which of the following statements comparing
 two-tier designs to spine

0:04:52.640000 --> 0:04:55.280000
 leaf designs are true?

0:04:55.280000 --> 0:05:00.120000
 Select two answers.

0:05:00.120000 --> 0:05:05.600000
 The correct answers are, unlike a spine
 leaf design in a two-tier design,

0:05:05.600000 --> 0:05:10.520000
 the distribution switches have redundant
 connections to each other.

0:05:10.520000 --> 0:05:16.200000
 And answer C. Unlike a two-tier design,
 in a spine leaf design, each leaf

0:05:16.200000 --> 0:05:24.020000
 switch has a connection
 to every spine switch.

0:05:24.020000 --> 0:05:33.780000
 Question eight. When an enterprise router
 or switch connects to a Metro

0:05:33.780000 --> 0:05:38.680000
 Ethernet network, what dictates the
 protocols and standards that can be

0:05:38.680000 --> 0:05:45.300000
 implemented on the Ethernet
 access link?

0:05:45.300000 --> 0:05:54.940000
 The correct answer is B, UNI, which stands
 for the User to Network Interface.

0:05:54.940000 --> 0:06:05.480000
 Question nine. In terms of Metro Ethernet,
 what term defines within the

0:06:05.480000 --> 0:06:11.200000
 service provider's Metro E cloud, which
 user or customer device is allowed

0:06:11.200000 --> 0:06:17.360000
 to communicate with
 other user devices?

0:06:17.360000 --> 0:06:23.880000
 The correct answer there is EVC, which
 stands for the Ethernet Virtual

0:06:23.880000 --> 0:06:36.280000
 Circuit. Question number ten.

0:06:36.280000 --> 0:06:42.260000
 Which type of Metro Ethernet service
 supports a full mesh between all

0:06:42.260000 --> 0:06:48.120000
 connected endpoints?

0:06:48.120000 --> 0:06:56.060000
 And the correct answer is an ELAN
 service, an Ethernet LAN service.

0:06:56.060000 --> 0:07:02.600000
 Question eleven.

0:07:02.600000 --> 0:07:10.280000
 Before or in front of which layer of the
 OSI model is an MPLS label applied?

0:07:10.280000 --> 0:07:18.600000
 The correct answer is an MPLS label is
 applied just in front of the layer

0:07:18.600000 --> 0:07:24.880000
 three header. That's why they sometimes
 call MPLS a layer 2.5 protocol,

0:07:24.880000 --> 0:07:30.220000
 because the header is applied right after
 the data link header, but before

0:07:30.220000 --> 0:07:34.880000
 the layer three header.

0:07:34.880000 --> 0:07:40.160000
 Question number twelve.

0:07:40.160000 --> 0:07:44.200000
 Which of the following statements about
 how service providers implement

0:07:44.200000 --> 0:07:46.900000
 MPLS networks are true?

0:07:46.900000 --> 0:07:53.480000
 Select two answers.

0:07:53.480000 --> 0:07:58.080000
 Answer A is true, customer edge routers
 form a routing relationship with

0:07:58.080000 --> 0:08:02.500000
 provider edge routers
 and answer D is true.

0:08:02.500000 --> 0:08:06.660000
 The MPLS network provides security
 by isolating data between different

0:08:06.660000 --> 0:08:13.800000
 customers. Recall that if this is our
 MPLS network, and let's say we have

0:08:13.800000 --> 0:08:20.360000
 two routers right here, we'll just
 call them X and Y, and they belong

0:08:20.360000 --> 0:08:24.420000
 to one particular customer.

0:08:24.420000 --> 0:08:30.040000
 And then connected to that same MPLS
 network is a different customer.

0:08:30.040000 --> 0:08:32.500000
 We'll just do those in the pink circles
 here, we'll just call that router

0:08:32.500000 --> 0:08:40.620000
 one and two. Okay, and let's make these
 green circles here represent the

0:08:40.620000 --> 0:08:45.080000
 provider edge routers that are
 connecting to the customer.

0:08:45.080000 --> 0:08:50.240000
 Everything inside this yellow circle
 here is being done with MPLS.

0:08:50.240000 --> 0:08:56.780000
 So recall that with MPLS, your customer
 edge routers, such as XY1 or two,

0:08:56.780000 --> 0:09:05.440000
 that forms an actual routing relationship
 with the provider edge router.

0:09:05.440000 --> 0:09:12.560000
 So you're doing OSPF, EIGRP, BGP directly
 with the provider edge router

0:09:12.560000 --> 0:09:18.520000
 itself. Secondly, MPLS by itself
 does not encrypt anything.

0:09:18.520000 --> 0:09:22.320000
 So when you send your data into the cloud,
 it's not going to be encrypted

0:09:22.320000 --> 0:09:26.040000
 as if it was going
 over an IPsec VPN.

0:09:26.040000 --> 0:09:30.740000
 What makes it secure and private is
 that when X sends its data into the

0:09:30.740000 --> 0:09:36.460000
 cloud, customer X and customer XY can
 be assured that their data will

0:09:36.460000 --> 0:09:40.620000
 never accidentally get over
 here to the pink customer.

0:09:40.620000 --> 0:09:44.100000
 There's no way it can be routed
 or seen by the pink customer.

0:09:44.100000 --> 0:09:45.800000
 The data paths are kept separate.

0:09:45.800000 --> 0:09:49.520000
 Even if the data is going along the
 same wire, even if there's some wire

0:09:49.520000 --> 0:09:53.860000
 right here and data going across that
 wire belongs to the two different

0:09:53.860000 --> 0:09:59.380000
 customers, it will never end up at
 the wrong customer edge router.

0:09:59.380000 --> 0:10:04.380000
 That's how privacy is maintained.

0:10:04.380000 --> 0:10:14.340000
 Question 13. Which type of access link
 technology is supported to connect

0:10:14.340000 --> 0:10:16.300000
 to an MPLS network?

0:10:16.300000 --> 0:10:22.680000
 The correct answer is all
 of these are correct.

0:10:22.680000 --> 0:10:26.940000
 That's why they call it multi-protocol
 label switching, because not only

0:10:26.940000 --> 0:10:32.680000
 can it apply labels to multiple protocols
 like IPv4 or IPv6 packets, but

0:10:32.680000 --> 0:10:36.960000
 also because MPLS could care less
 what your layer two protocol is.

0:10:36.960000 --> 0:10:40.900000
 It doesn't care if it's operating across
 an ethernet network, cable, serial,

0:10:40.900000 --> 0:10:43.760000
 it doesn't matter.

0:10:43.760000 --> 0:10:54.300000
 Question 14. In WAN technologies implemented
 by Telcos, what is the acronym

0:10:54.300000 --> 0:11:00.360000
 for the building where the
 Telco equipment resides?

0:11:00.360000 --> 0:11:07.820000
 The answer is CO, that
 is the central office.

0:11:07.820000 --> 0:11:19.520000
 Question 15. Which of the following statements
 are true about least lines?

0:11:19.520000 --> 0:11:25.980000
 Select two answers.

0:11:25.980000 --> 0:11:30.820000
 The correct answers are they sit at
 layer one of the OSI model, and they

0:11:30.820000 --> 0:11:34.300000
 do not define a data
 link layer protocol.

0:11:34.300000 --> 0:11:40.540000
 Most of the time people use PPP across
 a least line, but technically the

0:11:40.540000 --> 0:11:44.900000
 specifications for least lines don't
 make any mention about what layer

0:11:44.900000 --> 0:11:49.080000
 two headers and what layer two protocols
 should go across the least line.

0:11:49.080000 --> 0:11:53.800000
 A least line only specifies how it
 should be physically implemented at

0:11:53.800000 --> 0:11:58.220000
 layer one of the OSI model.

0:11:58.220000 --> 0:12:07.420000
 Question 16. Which of the following
 fields are used by HDLC to perform

0:12:07.420000 --> 0:12:09.280000
 error correction?

0:12:09.280000 --> 0:12:17.300000
 The correct answer is none
 of these are correct.

0:12:17.300000 --> 0:12:23.220000
 Now, while HDLC, much like ethernet,
 has a field in which it can detect

0:12:23.220000 --> 0:12:27.060000
 if there are errors, it can detect
 if the bits have been scrambled if

0:12:27.060000 --> 0:12:31.940000
 there's an error, there is no way that
 HDLC has the ability to fix that

0:12:31.940000 --> 0:12:35.580000
 error. All it can do is look at an incoming
 frame and say there's something

0:12:35.580000 --> 0:12:37.420000
 about this frame that's wrong.

0:12:37.420000 --> 0:12:40.460000
 In that case, the frame simply
 has to be discarded.

0:12:40.460000 --> 0:12:45.560000
 There's no way for HDLC itself to detect
 what the error is and fix it.

0:12:45.560000 --> 0:12:49.560000
 That's why the answer of none of these
 answers are correct was the correct

0:12:49.560000 --> 0:12:57.260000
 answer. Question 17.

0:12:57.260000 --> 0:13:06.620000
 Which of the following is not included
 in the list of five criteria for

0:13:06.620000 --> 0:13:12.500000
 a cloud computing service?

0:13:12.500000 --> 0:13:17.880000
 The correct answer is
 D, elastic routing.

0:13:17.880000 --> 0:13:22.580000
 Now, cloud computing services
 do have five criteria.

0:13:22.580000 --> 0:13:26.600000
 You can see four of them right
 here, A, B, C and E.

0:13:26.600000 --> 0:13:30.360000
 The fifth one that's missing is very
 similar to elastic routing, but it's

0:13:30.360000 --> 0:13:33.640000
 technically called
 rapid elasticity.

0:13:33.640000 --> 0:13:36.380000
 Rapid elasticity is the one
 that's missing from this.

0:13:36.380000 --> 0:13:44.360000
 So elastic routing, not a component
 of cloud computing services.

0:13:44.360000 --> 0:13:54.980000
 Question 18. In the context of the CCNA
 exam, which of the following statements

0:13:54.980000 --> 0:14:00.140000
 about on-premise private
 clouds are true?

0:14:00.140000 --> 0:14:06.040000
 Select the best answer.

0:14:06.040000 --> 0:14:11.460000
 So the best answer here is that the
 users who request the resources of

0:14:11.460000 --> 0:14:15.440000
 an on-premise private cloud and the
 people that create the private cloud

0:14:15.440000 --> 0:14:18.340000
 all work for the same company.

0:14:18.340000 --> 0:14:23.480000
 The key words here in the question
 was an on-premise private cloud.

0:14:23.480000 --> 0:14:28.060000
 If a private cloud is on-premise, then
 that means that everything that

0:14:28.060000 --> 0:14:32.360000
 creates that cloud, so the physical
 servers that are holding the virtual

0:14:32.360000 --> 0:14:37.940000
 machines, the software that can on
-demand create new virtual machines

0:14:37.940000 --> 0:14:43.000000
 or move virtual machines from one server
 to another, all of it is on-premise.

0:14:43.000000 --> 0:14:46.960000
 It's on your company's location, which
 means the people that are using

0:14:46.960000 --> 0:14:50.980000
 that service, as well as the people
 that maintain that service, all work

0:14:50.980000 --> 0:14:56.720000
 for the same company.

0:14:56.720000 --> 0:15:07.360000
 Question 19. Match the image with
 the correct service model.

0:15:07.360000 --> 0:15:11.980000
 So in this particular service model,
 you can see that the applications

0:15:11.980000 --> 0:15:18.540000
 are selected and installed by the customer
 and everything below that,

0:15:18.540000 --> 0:15:22.660000
 the operating system, stored CPU, RAM
 and network, that's all selected

0:15:22.660000 --> 0:15:23.680000
 by the customer.

0:15:23.680000 --> 0:15:27.280000
 They get to choose those various things,
 but they're actually provisioned

0:15:27.280000 --> 0:15:29.900000
 by the cloud provider themselves.

0:15:29.900000 --> 0:15:36.480000
 What service model does
 this represent?

0:15:36.480000 --> 0:15:43.300000
 This is what's described as infrastructure
 as a service, IaaS.

0:15:43.300000 --> 0:15:55.880000
 Question 20. Here we have another service
 model with a different image.

0:15:55.880000 --> 0:16:01.680000
 In this case, the applications are selected
 by the customer, but the customer

0:16:01.680000 --> 0:16:04.600000
 does not actually install
 them or maintain them.

0:16:04.600000 --> 0:16:07.440000
 They are, once they're selected,
 they are ready to go.

0:16:07.440000 --> 0:16:11.020000
 They are implemented and maintained by
 the cloud provider, and everything

0:16:11.020000 --> 0:16:16.360000
 beneath the application is completely
 transparent to the end customer.

0:16:16.360000 --> 0:16:23.400000
 What type of service
 model is this?

0:16:23.400000 --> 0:16:27.240000
 This is software as a service.

0:16:27.240000 --> 0:16:34.900000
 For example, when you use Gmail, you
 are using software as a service.

0:16:34.900000 --> 0:16:44.900000
 Question 21. Which of the following are
 the possible negative consequences

0:16:44.900000 --> 0:16:52.140000
 of moving your on-premise applications
 to a public cloud and connecting

0:16:52.140000 --> 0:16:57.320000
 to your cloud service using a
 public internet connection?

0:16:57.320000 --> 0:17:04.060000
 Select three answers.

0:17:04.060000 --> 0:17:06.920000
 And here are the three answers.

0:17:06.920000 --> 0:17:09.900000
 If you're going over the public internet,
 just a regular old internet

0:17:09.900000 --> 0:17:14.580000
 connection to get to your public cloud,
 there is no service level agreement.

0:17:14.580000 --> 0:17:18.780000
 There's no one who can guarantee you
 that your packets will take a certain

0:17:18.780000 --> 0:17:23.640000
 minimum delay or anything like that,
 so there is no WAN SLA available.

0:17:23.640000 --> 0:17:26.340000
 Also, there was certainly
 decreased security.

0:17:26.340000 --> 0:17:30.520000
 Anytime you go across the public internet,
 you are decreasing your security

0:17:30.520000 --> 0:17:34.660000
 as opposed to if you had access those
 resources on-premises within your

0:17:34.660000 --> 0:17:36.600000
 own company itself.

0:17:36.600000 --> 0:17:39.960000
 And then lastly, once again, if you're
 going over the public internet,

0:17:39.960000 --> 0:17:43.540000
 you have very little, if anything, you
 can do from a quality of service

0:17:43.540000 --> 0:17:47.520000
 perspective. You really can't control
 your packets and make sure that

0:17:47.520000 --> 0:17:52.520000
 your packets are prioritized before
 or after anybody else's packets when

0:17:52.520000 --> 0:17:52.780000
 you're going to go to
 your own company.

0:17:52.780000 --> 0:17:57.980000
 So, we're going across
 the internet.

0:17:57.980000 --> 0:18:09.340000
 Question 22. A provider offers private
 WAN connections, for example, MPLS,

0:18:09.340000 --> 0:18:11.880000
 Metro Ethernet, etc.,
 to consumers.

0:18:11.880000 --> 0:18:19.020000
 The same private WAN also has connections
 to multiple public cloud providers.

0:18:19.020000 --> 0:18:21.700000
 This type of service is called...

0:18:21.700000 --> 0:18:32.220000
 The answer is this is called
 an intercloud exchange.

0:18:32.220000 --> 0:18:41.920000
 Question 23. And this is our
 last question for this video.

0:18:41.920000 --> 0:18:47.500000
 Fill in each cell with either true or
 false as it pertains to the methods

0:18:47.500000 --> 0:18:51.260000
 available for connecting
 to public clouds.

0:18:51.260000 --> 0:18:55.240000
 So, what I want you to do in this question
 is, for example, look at the

0:18:55.240000 --> 0:18:59.600000
 first row of makes data private.

0:18:59.600000 --> 0:19:04.880000
 So, if you're connecting to a public
 cloud directly across the internet,

0:19:04.880000 --> 0:19:06.640000
 does that make your data private?

0:19:06.640000 --> 0:19:10.220000
 If the answer is yes and that you would
 mark true in that cell, if the

0:19:10.220000 --> 0:19:12.720000
 answer is no, you
 would mark false.

0:19:12.720000 --> 0:19:16.700000
 What if you're connecting to that
 public cloud over an internet VPN?

0:19:16.700000 --> 0:19:19.320000
 Does that make your data private?

0:19:19.320000 --> 0:19:24.100000
 So, look at each one of these cells and
 ask yourself, is it true or false

0:19:24.100000 --> 0:19:29.360000
 about connecting to a public cloud with
 regards to these five different

0:19:29.360000 --> 0:19:33.340000
 ways or methods that I could
 connect to that public cloud?

0:19:33.340000 --> 0:19:36.800000
 So, definitely want to pause this slide,
 maybe even take a screenshot

0:19:36.800000 --> 0:19:42.600000
 of it or look at your PDF and the learner
 or the course resources file

0:19:42.600000 --> 0:19:49.020000
 and then mark the cells
 appropriately.

0:19:49.020000 --> 0:19:50.880000
 And here are the answers.

0:19:50.880000 --> 0:19:55.180000
 So, for connecting to a public cloud,
 does it make your data private?

0:19:55.180000 --> 0:19:58.340000
 Well, if you're going across
 the internet, definitely not.

0:19:58.340000 --> 0:20:02.280000
 If you're doing an internet VPN using
 like IPsec or something, yes, it

0:20:02.280000 --> 0:20:06.740000
 does. And all the other methods of MPLS
 VPN, Ethernet, WAN and intercloud

0:20:06.740000 --> 0:20:12.220000
 exchange, yes. Those are those make your
 data private in one way or another.

0:20:12.220000 --> 0:20:15.980000
 Is QOS supported when you're
 going to the public cloud?

0:20:15.980000 --> 0:20:19.320000
 Well, if you're going across the internet
 at all, whether it be an internet,

0:20:19.320000 --> 0:20:24.280000
 just a plane internet connection or
 an internet VPN, there is no QOS.

0:20:24.280000 --> 0:20:28.220000
 But there is QOS when you're using
 the other three methods.

0:20:28.220000 --> 0:20:32.260000
 Does it require capacity planning?


0:20:32.260000 --> 0:20:37.340000
 And then there was, do we have to think
 about, do I need more bandwidth?

0:20:37.340000 --> 0:20:41.000000
 And the answer is true
 for all of these.

0:20:41.000000 --> 0:20:43.620000
 Whether you're connecting to your public
 cloud via the internet or all

0:20:43.620000 --> 0:20:48.040000
 the way to an intercloud exchange,
 you're talking now about more data

0:20:48.040000 --> 0:20:52.880000
 leaving your company with the destination
 of some resources in the public

0:20:52.880000 --> 0:20:57.260000
 cloud. That's going to consume
 more WAN bandwidth.

0:20:57.260000 --> 0:21:01.000000
 And so it is going to require
 some capacity planning.

0:21:01.000000 --> 0:21:04.700000
 What about easing migration
 to a new cloud provider?

0:21:04.700000 --> 0:21:11.440000
 Well, if we're connecting via the internet
 or an internet VPN to a public

0:21:11.440000 --> 0:21:16.120000
 cloud, yes, we can move to a brand new
 public cloud with a different provider

0:21:16.120000 --> 0:21:20.700000
 very easily. If we're using intercloud
 exchange at the very end, the whole

0:21:20.700000 --> 0:21:26.200000
 purpose of an intercloud exchange is to
 allow you to easily move to different

0:21:26.200000 --> 0:21:28.860000
 cloud providers using
 public clouds.

0:21:28.860000 --> 0:21:33.260000
 Now, if you're using an MPLS VPN or
 an Ethernet WAN, those are resources

0:21:33.260000 --> 0:21:37.520000
 that took a lot of time and energy
 to set up a lot of planning moving

0:21:37.520000 --> 0:21:41.900000
 away from those to some other type
 of connection is not easy.

0:21:41.900000 --> 0:21:44.260000
 So it does not ease migration.

0:21:44.260000 --> 0:21:46.700000
 What about initial installation?

0:21:46.700000 --> 0:21:48.100000
 Which one of these is fast?

0:21:48.100000 --> 0:21:49.940000
 Which one is slow?

0:21:49.940000 --> 0:21:54.960000
 Well, using any internet-based connection,
 for example, internet or internet

0:21:54.960000 --> 0:21:59.320000
 VPN very fast, you can connect to a
 public cloud over the internet or

0:21:59.320000 --> 0:22:02.680000
 over an internet VPN connection in a
 matter of minutes with very simple

0:22:02.680000 --> 0:22:07.580000
 setup. However, if you want to use MPLS
 VPN, Ethernet WAN or an intercloud

0:22:07.580000 --> 0:22:13.460000
 exchange, that takes quite a bit more
 time to do your initial installation

0:22:13.460000 --> 0:22:16.000000
 and get that running.

0:22:16.000000 --> 0:22:20.660000
 Thank you for watching, and I hope
 this was a good assessment for you

0:22:20.660000 --> 0:22:22.300000
 on these particular technologies.