Hello and welcome back to Sai Berries. 2019 Comp Tier Security Plus Certification Preparation course.
We're going to continue our discussion on Marginal my three, which is in fact domain three. And the top of discussion will be architecture and design.
Surprisingly enough, we have a brand new learning objective, which is 3.8, where we have to explain how resiliency and automation scribes you reduce risk.
The first item on our agenda is a pre assessment quiz, and it reads as follows. What dust abbreviation raid represent? Is it a redundant array? Off Adi drives
Be resilient architecture for interdependent disk.
It wasn't see redundant array off independent drives or D resistant architecture off. Enter related data storage.
If you said like to see you absolutely correct, because is redundant. Array off independent drives
continue on without discussion on this particular brand new learning objective, which is simply title. Explain how resiliency and automation scratch it. Reduce your risk. Here again are the topics which encompasses this particular new learning objective.
The first they want to take a look. It's called automation and scripting.
To automate. You need to use cold scripts, third party application or a mix of all three and automation script consists of a launch point variables with corresponding binding values and a source code. You can also create library scripts, which are reusable pieces off programmable language,
the automate scripts that can invoke from the body
Here again, let's take a look at three different types of automation scripting. We have automated course of action.
In this case, you can also automate the course of action based upon a step by step set of tasks such as appoint a new server or based on specific events that occur, such as a service crashing.
Continuous marking basically is the act of monitor your vomit on a 24 7
configuration. Validation is a process to look for configuration drift when a server service no longer matches the initial or desire configuration.
Now, if you want to roll out a an application instance, for example, Now you want to rule out, for example, hundreds of those applications you can build them from scratch. You you can't build it from scratch each every time, so instead what you're gonna do, you gonna use a template to be able to build a basic structure of an application instance, which makes it very easy, then to deplore.
So each time you deplore new server, you configure the Web server with that particular template.
is a copy of the properly configured and secure computer software system that can be replicated to other computers. Hence the term a master image
continuing with that discussion. 3.8 Learning objective, which again explain how resiliency and automation strategy reduce risk here again on some topics with we're gonna highlight doing this particular portion of the video, we could begin by discussing what is none persistent all way down to lie boot media.
So without further ado, let's define exactly what non persistence all about. Now this is data, which is not available at the fully closed application is referred to as non persistent.
In other words, if you shut down your computer, all your debt remains as on your heart drop. You have persistent if it remains there.
If when you shut down your computer, on the other hand, all the contents of your computer memories erased that's considered non persistent.
Here, get us some examples of what we call non persistent. We have snapshots, not a snapshot of a state of virtual machine can be saved for later use because that's non persistent. If you turn it off, you're gonna lose it.
Revert to know state basically is was stolen a device to his previous secure condition.
Then we have rolled back to know configuration
basically what you do, your undue recent changes that cause errors or weaken the security.
We have a live boot media with basically, that's a lightweight bookable image on us. Be USB drive in other words or memory stick or flash drive or some type of optical media
continue on without discussion. Get off this particular objective, displaying how resiliency and automation scratch it. Reduce risk here, getting some brand new
topics which was encompasses this particular
We were talking a bit or speak about the topic. Dog elasticity,
this creative allocation as well.
When we think about elasticity,
it's the billy of Enterprise Data Centre to revert to a former size at the expanding. In fact, it's the price of revision. New resource is to meet additional demands such as adding a Web server to provide additional resource is doing the holiday.
Another example, Be scalability. In fact, this is a $1,000,000,000 company to grow while maintaining a resilient infrastructure.
Basic scalable is like elasticity, but deals only with increasing resource is not decreasing them.
Descriptive allocation. Basically, it refers to spreading the risk
redundancy basis, having multiple components to reduce the impact of a system failure. In other words, you're not gonna have to ensure that you will have a single point of failure
again. It's the use of duplicate equipment like, for example,
whether the having only one deeply server that if it wants to crash your whole network is basically render useless. You don't have to DC service and not ensure is what we call redundancy.
Fault. Tolerance is a system ability to deal whit malfunction,
fault tolerance where it doesn't ableto sister to continue to function, even if a fair cure in a particular component,
high availability a system that can function for extended period time with little or no downtime is considered high availability.
Rain is a technology that uses multiple heart dis drive for increased reliability as well as performance.
The next item, Arjuna is a post assessment quiz. Now what you need to determine based upon this particular quiz here, you need to determine whether or not the statement is either a true statement
or, in fact, a false statement. And it reads as follows. A system that can function for an extended period of time with little downtime can best be described as high availability.
Is that true or false?
If you said, Let the truth, you're absolutely correct.
Let's not turn our teacher tour key takeaways from this particular video,
and they are as follows.
We learned that high availability is a system that can function for an extended period of time with little downtime.
In addition, we learned that fault tolerance is assistant ability to deal with malfunctions.
We learned that rate is a technology that uses multiple hard disk drive for increased reliability and performance.
We learned that scalability is ability of a company to grow while maintaining a resilient infrastructure.
We learned that redundancy is having multiple components to reduce the impact off a system failure.
We also learned that ability of enterprise deficit to revert to a former size at the expanding
and our upcoming video will be taking a look at a brand new learning objective, which is 3.9, which specific states explain the importance of physical security controls.
I look forward to seeing you in a very next video.