70-300 Analyzing Requirements And Defining Microsoft .net Solution Architectures Pt.6

Front 1

What is an attribute?

Back 1

a characteristic of an entity that describes the entity in some way

Front 2

In a data model, when can a weak only exist?

Back 2

only in relationships with other entities

Front 3

Which type of logical relationship is being described when each region can have one or more salespeople and each salesperson can sell in one or more regions?

Back 3

a many-to-many relationship

Front 4

Should you use a normalized or a denormalized database for write-intensive databases?

Back 4

normalized

Front 5

What are the deliverable outputs of the logical design?

Back 5

a logical object model, a logical data model, and a high-level UI design

Front 6

What is the purpose of a primary key?

Back 6

It uniquely identifies each row in a database table.

Front 7

Which action(s) does Microsoft recommend for validating your logical design?

Back 7

Review the use cases and usage scenarios.

Front 8

In an ER diagram, how is a weak entity represented?

Back 8

a rectangle with a double border

Front 9

Should you use a normalized or a denormalized database in an online transaction processing(OLTP) system to capture historical transactional data?

Back 9

denormalized

Front 10

Which type of logical relationship would be used when each row from one table relates to only one row from a second table and vice versa?

Back 10

a one-to-one relationship

Front 11

Should you use a normalized or a denormalized database for read-intensive databases?

Back 11

denormalized

Front 12

What is normalization?

Back 12

the process of eliminating data redundancy in a database design

Front 13

Why would it be beneficial to create a proof of concept?

Back 13

to verify that a project is possible and to reduce the risk of project failure

Front 14

Which type of logical relationship would be used when each row from one table relates to one or more rows from a second table?

Back 14

a one-to-many relationship

Front 15

How must your data be normalized to be in third normal form (3NF)?

Back 15

The database must be in second normal form and NOT have a non-key column depend on another non-key column.

Front 16

In an ER diagram, what does a circle at the end of a relationship line represent?

Back 16

that the relationship is optional

Front 17

In a logical data model, which database element represents an entity?

Back 17

a table

Front 18

In an ER diagram, how do you represent the many sides of a relationship line?

Back 18

using a crow's foot

Front 19

Which type of logical relationship can only be physically implemented using a junction table?

Back 19

a many-to-many relationship

Front 20

Is a cascading constraint necessary to enforce data integrity?

Back 20

No. While you might want to cascade updates or deletes, you could prevent them altogether, so this is not required.

Front 21

To what does the term "cardinality" refer?

Back 21

the number of instances of one entity that can or must be associated with each instance of a second entity

Front 22

How is having no data redundancy beneficial to your database?

Back 22

It ensures data integrity.

Front 23

What are the benefits of choosing the most appropriate data type for a data element in a database?

Back 23

Selecting the most appropriate data type assists with data validation and optimizes storage in the database.

Front 24

What is the purpose of a foreign key?

Back 24

It establishes and enforces a relationship between the data in two database tables.

Front 25

How can you ensure your database is in second normal form (2NF)?

Back 25

The database must be in first normal form and have every non-key column depend on the entire primary key.

Front 26

Which type of integrity ensures values for a given column are valid?

Back 26

domain integrity

Front 27

Which guidelines should you follow to optimize the use of transactions?

Back 27

Each transaction should be as short-lived as possible, include only what is required, and if possible not be distributed.

Front 28

In an ER diagram, how is a regular entity represented?

Back 28

a rectangle with a single border

Front 29

When determining the level of normalization for a database, what is the recommended maximum number of tables that should be used in a frequent query?

Back 29

4

Front 30

What should you do if you want the data in two columns to uniquely identify each row?

Back 30

Create a composite, primary key using the two columns.

Front 31

How is it beneficial to queries in your database to have denormalized tables?

Back 31

It optimizes queries. Because fewer joins are necessary, queries are usually faster.

Front 32

What is a federated database?

Back 32

a database that is partitioned into different instances and can run on different physical machines

Front 33

Which term refers to the logical connection between two entities?

Back 33

relationship

Front 34

How can you ensure your database is in first normal form (1NF)?

Back 34

Ensure it has no repeating groups or multi-values columns.

Front 35

How should you design a junction table to implement a many-to-many relationship between two tables?

Back 35

You should create a composite primary key for the junction table that consists of the primary keys from the other two tables. You can also add any other columns to the junction table that are needed.

Front 36

What is denormalization?

Back 36

Denormalization is the process of including redundancy in a database design, usually to improve performance. Denormalization results in tables with fewer fields requiring fewer joins.

Front 37

How is having indexed columns beneficial to your database?

Back 37

It allows for faster queries and faster sorting.