Domain 7 Test Notes Flashcards

(33 cards)

1
Q

Any event that stops, prevents, or interrupts an organization’s ability to perform its work task.

A

Diasater

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Anything caused by nature, this could be earthquakes, floods, snow, tornados.

A

Natural Disaster

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Anything caused by humans, they can be intentional or unintentional

A

Human Disaster

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Anything in our environment, could be power outage/spikes, hardware failures, provider issues

A

Environmental Disaster

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

An observable change in state, is neither negative nor positive. Examples- system powered on or an application started

A

Event

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Triggers warning if certain event happens.. Examples - traffic utilization above 75% or Memory usage at 90% for more than 2 minutes.

A

Alert

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Multiple adverse events happening on a system or network

A

Incident

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

CISSP Incident Management Steps

A

Detection
Response
Mitigation
Reporting
Recovery
Remediation
Lesson Learned
DRMRRRL

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Is one of the simplest tests to conduct. Managers and functional areas go through the plan to check a list of components needed for the recovery process

A

Read-Through (Checklist)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Members of the disaster recovery team gather and role play a disaster scenario. Also called tabletop exercise

A

Structured Walk-Through

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The disaster recovery team is presented with a scenario and asked to develop an appropriate response. Some of the responses may be tested.

A

Simulation Test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Critical components are brought up at a secondary site using backups while the same systems are up at the primary site.

A

Parallel Test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

All operations are interrupted at the primary site and shifted to the recovery site.

A

Full Interruption Test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Called Striping. It uses 2 or more disks and improves the disk subsystem performance, doesn’t provide fault tolerance

A

RAID -0

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Called Mirroring. It uses 2 disks, which both hold the same data. If one disk fails, the other disk includes the data so that the system can continue to operate.

A

RAID-1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Called Striping with parity. It uses 3 or more disks with the equivalent of one disk holding parity information which allows the reconstruction of data through calculations if a single disk is lost.

17
Q

Called stripe of mirrors. It is configured as two or more mirrors with each mirror configured in a striped configuration. It uses at least 4 disks. There has to be an even number of disks.

18
Q

Database backups are moved to a remote site using bulk transfers.

A

Electronic Vaulting

19
Q

Data transfers are performed in a more expeditious manner. Data transfers still occur in a bulk transfer mode but they occur on a more frequent basis usually once every hour.

A

Remote Journaling

20
Q

a live database server is maintained at the backup site. The remote server receives copies of the database modifications at the same time they are applied to the production server at the primary site

A

Remote Mirroring

21
Q

Backups everything regardless of the setting of the archive bit. The archive bit is reset, turned off, or set to 0

22
Q

Backups only those files that have been modified since the time of the most recent full or incremental backup. The archive bit is reset, turned off, or set to 0 after this backup runs. Faster to backup but need more tapes to restore.

A

Incremental Backup

23
Q

Backup all files that have been modified since the time of the more recent full backup. Don’t clear the archive bit. Backups take more time to run but require less tapes to restore.

A

Differential Backup

24
Q

A full backup that doesn’t clear the archive bit. Often performed before system updates, patches, etc

25
How long a new or repaired system or component will function on average before failing
Mean Time Between Failures (MTBF)
26
How long it will take to recover a failed system
Mean Time to Repair (MTTR)
27
The acceptable amount of data that can not be recovered
Recovery Point Objective (RPO)
28
The time to rebuild the system and configure it for reinsertion into production. The amount of time the organization can survive without without an asset or process.
Maximum Tolerable Downtime (MTD)
29
The amount of time to restore the system (hardware)
Recovery Time Objective
30
A basic change management process where users request changes, which are then analyzed for cost/benefit by managers and prioritized by developers for implementation.
Request Control
31
A basic change management process where developers recreate issues, develop solutions in a controlled environment, ensure quality, and document changes before deployment.
Change Control
32
A basic change management process where changes are approved, any temporary code is removed, and only vetted changes are released to production after acceptance testing.
Release Control
33
The rule states that when an agreement between two parties is put into written form, it is assumed to be the entire agreement unless amended in writing.
Parol evidence