- Welcome to lesson 10, deep dive quiz.
Now, lesson 10 was all about comparing
and contrasting security implications
of different architecture models.
So we explored a number of different architectures.
In lesson 10.1,
we did a survey of different computing architectures.
In lesson 10.2,
we looked at cloud services from a consumer perspective.
In lesson 10.3, we looked at the cloud infrastructure.
In lesson 10.4,
we focused in on our data center solution elements
with a real heavy focus on automation.
In 10.5, we explored virtualization.
In 10.6, I introduced you to embedded systems
and we looked at industrial control systems
and SCADA systems.
And then we carried over looking at embedded systems
right into lesson 10.7
when we looked at the internet of things,
which is an embedded system as well as IIOT,
the industrial internet of things.
So that takes us to a 10 question quiz.
So make sure you've got a pen
or a pencil and a piece of paper.
Put me on pause as often as you need to.
I really want you to work through these answers on your own.
And then take me off pause
and go through it with me together.
So let's get our quiz started.
Question one,
on demand and temporary use of the public cloud
when demand exceeds resources available
in a private cloud or on-premises infrastructure,
is this cloud bursting, elasticity, high availability,
or resource pooling?
Which answer do you like?
If you need to, don't hesitate to put me on pause.
The on-demand and temporary use, right, of the public cloud
when demand exceeds resources either available
in our private cloud or in our on-premises infrastructure.
Cloud bursting, elasticity, high availability,
resource pooling.
I'm gonna choose cloud bursting.
Now, elasticity often refers to the ability
to add more resources and take them away.
High availability ensures
that the systems are always available.
And resource pooling really refers
to being able to virtualize our systems
and be able to sort of manage, mix and match, if you will,
our resources.
But I believe this one is gonna be cloud bursting.
Do you agree?
Let's check.
And that is correct.
Question two.
You have recently joined ACME Oil and Gas.
You are dismayed to find that security patches
are no longer available for the in the field devices
because of the age of the operating system.
How would you most likely describe this architecture?
So it's oil and gas, it's an old system,
and it's out in the field.
An embedded system, client/server, a mainframe,
or an ICS or SCADA system.
So how are you going to describe the architecture itself?
Embedded, client/server, mainframe, or ICS/SCADA?
Well, it is an embedded system
but that doesn't really tell us enough.
It's not client/server.
It's probably not a mainframe.
Ah, because it is oil and gas,
it's old and it's in the field,
my guess is it's an ICS/SCADA system.
You like that one?
Let's try it.
There we go.
All right, question three.
The cloud infrastructure is comprised of multiple layers.
I want you to choose all that apply.
A security layer, a community layer, a virtual layer,
or a physical host layer.
So the cloud infrastructure itself, right,
comprised of multiple layers.
I want you to choose the ones that apply.
Security layer, community layer, virtual layer,
or physical host layer.
Go ahead, take your time.
Well, I'm gonna choose a physical host layer
because that's the physical devices, right?
The physical computing equipment
and all of the ancillary equipment.
And then from that physical host,
we are going to virtualize components
to be able to create our resource pool
to be able to dynamically allocate resources
to our users as they need it.
So the physical host layer and the virtual layer.
That's what I believe are the two layers, right,
in our cloud infrastructure.
You agree?
Let's check it.
And that is correct.
Question four.
This logical mechanism packages together
everything needed to run a small piece of software.
A private cloud, a container, a virtual machine,
or a hypervisor.
Private cloud, container,
virtual machine, or hypervisor.
What are you gonna choose?
I'm gonna choose a container, right?
Everything we need to run a small piece of software, right?
It's not really the private cloud.
Private cloud is just the cloud for exclusive use, you know,
of a particular group.
It's not necessarily a virtual machine, VM, right?
Just refers to the fact
that we're going to virtualize, you know, a machine
from a host system.
Hypervisor is what actually allows us
to virtualize containers what we're looking for here.
Agree?
Let's check.
And that's correct.
All right.
Question five.
Ooh, we got a lot of matching to do here.
We're gonna match the following cloud related terms
and their descriptions.
You are definitely gonna have to put me on pause for this
and get out a piece of paper.
On the left hand side, we have a private cloud, SaaS,
That's software as a service.
IAAS, infrastructure as a service.
A community cloud.
PaaS, platform as a service.
And the public cloud.
On the right hand side,
we have customers provision bare metal resources,
customers deploy onto the cloud infrastructure,
provisioned for a well-defined group,
customers use the provider's application,
provision for single organization exclusive use,
and provision for public use.
So put me on pause,
come on back when you got 'em all matched up.
All right, I'm gonna start right up on the top
on the right hand side.
Customers provision bare metal resources.
Well, that sounds a lot to me like IaaS.
So there we go.
Provisioned for a well-defined group.
Well, a well-defined group must be a community.
So let's go to a community cloud.
Customers use the provider's application.
Right, so they're signing on
and just using the application provided by the provider.
Sounds a lot like software as a service or SaaS.
Customers deploy,
and by this point, we probably mean deploy applications
if they have either acquired
or created onto the cloud infrastructure.
It sounds a lot like PaaS, platform as a service.
Oh, provision for single organization exclusive use.
Well, that's very private.
And right there is our private cloud.
And lastly, we have provision for public use.
Well, that's our public cloud.
So let's go right down to these private cloud provision
for a single organization's exclusive use.
SaaS, software as a service,
customers use of providers application.
IaaS infrastructure as a service,
customers provision bare metal resources.
A community cloud, provision for a well-defined group.
PaaS, platform as a service,
customers deploy onto the cloud infrastructure.
And a public cloud, which is provisioned for public use.
Agree?
Well, let's check it out.
Awesome, we got 'em all right.
Question six.
Which component is not, again, that word not,
considered to be part of a closed-loop embedded system?
That means three of these
are part of a closed-loop embedded system and one is not.
A printer interface.
The device specific application.
An RTOS.
Or an SoC.
Now, RTOS was a real-time operating system.
SoC was system on a chip.
Three of those are part of a closed-loop embedded system.
One is not.
Which one isn't?
Well, let's see.
System on a chip, that's definitely part of our closed-loop.
RTOS, definitely part of our closed-loop.
And this piece of software, the application,
part of our closed-loop.
So what's not part of our closed-loop?
Right there, our printer interface.
You agree?
All right, let's check it out.
And we are correct.
Okay, we are gonna drag and drop terms
to describe IOT systems.
And I'm gonna read you each of the sentences
and then it'll be a great time to put me on pause
and figure out what word goes where.
Blank is the foundation of an IOT device.
Blank detect and response to changes in the environment.
Blank translate electrical signals into physical action.
Blank are used to send and receive RF signals.
And blank is how IOT devices communicate with each other.
And our terms we have to use are VNC, embedded systems,
transceivers, RTOS, SOC, actuators, sensors,
and smart connectivity.
Now, there's more terms there
than we're actually going to use.
So put me on pause,
figure out how to finish these sentences, then come on back.
We'll do it together.
All right, the foundation of an IOT device,
well, that's gonna be an embedded system, right?
The embedded system is a foundation of an IOT device.
Blanks detect and respond to changes in the environment.
That's gonna be sensors.
Sensors are what detect and respond
to changes in the environment.
Blank translate electrical signals into physical signals.
That's the job of an actuator.
Blank is used to send and receive RF signals.
That's a job of a transceiver.
And blank is how IOT devices communicate with each other.
And the term that we use for how they communicate
with each other is going to be smart connectivity.
So we're not using term VNC, RTOS or SOC.
So an embedded system is the foundation of an IOT device.
Sensors detect and respond to changes in the environment.
Actuators translate electrical signals into physical action.
Transceivers are used to send and receive RF signals.
And smart connectivity is how IOT devices communicate
with each other.
Do you get 'em all?
All right, let's check our work.
And that's correct.
All right, question eight.
This situation occurs when the number of virtual machines
is out of control.
Is it virtualization sprawl, over allocation,
virtual machine escape, or network virtualization?
So this is why we just keep standing up VMs
over and over again.
We've just got so many of them, right?
Is this referred to as virtualization sprawl,
over allocation, virtual machine escape,
or network virtualization?
Well, right away,
you should be able to eliminate at least a couple here.
We're gonna eliminate network virtualization
because that just isn't relevant to our question.
And over allocation, which is kind of a cool sounding term
but it isn't really a term.
It's just one we made up.
So now we're between virtualization sprawl
and virtual machine escape.
Well, virtual machine escape is when there is communication
between the virtual machine and the host systems,
and that should never ever happen.
Think about the VM kind of escaped out of its boundaries
and now it's interacting with the host system.
The one I'm gonna choose here
is going to be virtualization sprawl.
And that's when the number of virtual machines
just gets out of control.
And we have so many, we might have licensing issues,
we might not be managing 'em appropriately.
We might not be including them, you know
in our patch management or our vulnerability
'cause there's just so many out there.
So virtualization sprawl, let's check it.
And that is correct.
Another matching.
This one is we're gonna match
the following solution elements with their descriptions.
We talked about all these
when we talked about data center solution elements.
We have orchestration, serverless computing, microservices,
and infrastructure as code.
Those are the solution elements.
Descriptions down the right hand side.
The integration of disparate tools and platforms
for an automated response.
Dynamic allocation of execution resources.
Independent deployable components.
Or codes used to automate provisioning.
Well, even though this is randomized
this is a little weird because what's gonna happen here?
Can you tell right away how these are gonna match up?
Yeah, pretty exact.
All right, let's try it.
Orchestration.
Well, that is the integration of disparate tools
and platforms for an automated response.
Serverless computing,
well, that is dynamic allocation of execution resources.
Microservices.
Well, that actually is independent deployable components.
And infrastructure's code,
well, that's using code to automate provisioning.
So going through these again.
Orchestration is that integration of disparate tools
and platforms for an automated response.
Serverless computing,
dynamic allocation of execution resources.
Microservices, independent deployable components.
And infrastructure's code,
using code to automate provisioning.
That was kind of an easy one for us, wasn't it?
All right, let's check it out.
And that is correct.
All right, our last question.
The ability to fit resources needed to cope
with loads dynamically
by provisioning and deprovisioning resources.
So more resources, less resources.
More resources, less.
Is a serverless, elasticity,
pay-per-use, or scalability.
For provisioning and deprovisioning.
Go ahead and make that choice.
What do you think?
I'm gonna choose elasticity.
Really, your two choices there,
we're thinking about elasticity or scalability.
Scalability we often refer to as scaling, upper scaling out,
where elasticity, think about that elastic band, right?
That we stretch out and comes back,
stretch out and comes back.
That's the ability to dynamically provision
and deprovision resources.
Let's just double check that it's right.
And it is.
Awesome.
All right, great job.
We just did 10 questions together.
I hope that you learned a little bit more
or reinforced your knowledge.
That's really why we do these
and that you, you know take the time to put me on pause
and write down your own answers
that you really do make these quizzes
an interactive experience.
Okay, up next, we're gonna go into lesson 11.
Given the scenario,
apply security principles to secure the enterprise.
I'll see you there.