Explanation/Reference:
Explanation:
Normalizing data within a database does not eliminate duplicate key fields by putting them into separate tables.
An entity is in First Normal Form (1NF) when all tables are two-dimensional with no repeating groups.
A row is in first normal form (1NF) if all underlying domains contain atomic values only. 1NF eliminates repeating groups by putting each into a separate table and connecting them with a one-to-many relationship. Make a separate table for each set of related attributes and uniquely identify each record with a primary key.
Eliminate duplicative columns from the same table.

Create separate tables for each group of related data and identify each row with a unique column or set

of columns (the primary key).
An entity is in Second Normal Form (2NF) when it meets the requirement of being in First Normal Form (1NF) and additionally:
Does not have a composite primary key. Meaning that the primary key cannot be subdivided into

separate logical entities.
All the non-key columns are functionally dependent on the entire primary key.

A row is in second normal form if, and only if, it is in first normal form and every non-key attribute is fully

dependent on the key.
2NF eliminates functional dependencies on a partial key by putting the fields in a separate table from

those that are dependent on the whole key. An example is resolving many:many relationships using an intersecting entity
An entity is in Third Normal Form (3NF) when it meets the requirement of being in Second Normal Form (2NF) and additionally:
Functional dependencies on non-key fields are eliminated by putting them in a separate table. At this

level, all non-key fields are dependent on the primary key.
A row is in third normal form if and only if it is in second normal form and if attributes that do not

contribute to a description of the primary key are move into a separate table. An example is creating look-up tables.
Incorrect Answers:
A: Normalizing data within a database does eliminate duplicative columns from the same table.
B: Normalizing data within a database does eliminate functional dependencies on a partial key by putting the fields in a separate table from those that are dependent on the whole key.
C: Normalizing data within a database does eliminate Functional dependencies on non-key fields by putting them in a separate table.
References:
http://psoug.org/reference/normalization.html
http://searchsqlserver.techtarget.com/definition/normalization?vgnextfmt=print

A watering hole attack is a type of attack that targets a specific group of users by compromising a website that they frequently visit. The attacker then uses the compromised website to deliver malware or exploit code to the visitors, hoping to infect their systems and gain access to their networks or data. A watering hole attack is dependent upon the compromise of a secondary target (the website) in order to reach the primary target (the users). A brute force attack, a spear phishing attack, and an Address Resolution Protocol (ARP) poisoning attack are not dependent on compromising a secondary target. References:
* [7]: CISSP CBK, 4th edition, page 431
* [8]: CISSP Official (ISC)2 Practice Tests, 3rd edition, page 129

The risk assessment is critical because it enables the person responsible for contingency planning to focus risk management efforts and resources in a prioritized manner only on the identified risks. The risk management process includes the risk assessment and determination of suitable technical, management, and operational security controls based on the level of threat the risk imposes. Business units should be included in this process. Source: SWANSON, Marianne, & al., National Institute of Standards and Technology (NIST), NIST Special Publication 800-34, Contingency Planning Guide for Information Technology Systems, December 2001 (page 7).

SET was developed by a consortium including Visa and MasterCard.
Source: Harris, Shon, CISSP All In One Exam Guide, pages 668-669.
Mondex is a smart card electronic cash system owned by MasterCard.
SSH-2 is a secure, efficient, and portable version of SSH (Secure Shell) which is a secure
replacement for telnet.
Secure HTTP is a secure message-oriented communications protocol designed for use in
conjunction with HTTP. It is designed to coexist with HTTP's messaging model and to be easily
integrated with HTTP applications.