All categories

1 year ago

Where does an MPLS label go in a PDU?

Computers and Technology

1 answer:

Natalija [7]1 year ago

6 0

Answer: Between Layers 2 and 3

Explanation:

In between Layer 2 and Layer 3 the MPLS header is present and is known as Shim header. It is also said to be in 2.5.

You might be interested in

g Suppose the information content of a packet is the bit pattern 1110 0110 1001 1101 and an even parity scheme is being used. Wh

erma4kov [3.2K]

Answer: see description

Explanation:

first we accommodate the bit pattern in a matrix of 4x4 which is the minimum length checksum field, now with even parity two-dimensional scheme we need to complete this matrix by adding one row and one column by adding at the end of each row a 1 or a 0 to complete pairs of 1's:

we have

$\left[\begin{array}{cccc}1&1&1&0\\0&1&1&0\\1&0&0&1\\1&1&0&1\end{array}\right]$

so we complete with this, adding a row at the end which matches a pair number of 1's

$\left[\begin{array}{ccccc}1&1&1&0&1\\0&1&1&0&0\\1&0&0&1&0\\1&1&0&1&1\\1&1&0&0&0\end{array}\right]$

4 0

2 years ago

Consider the following relation:CAR_SALE(Car#, Date_sold, Salesperson#, Commission%, Discount_amt)Assume that a car may be sold

GalinKa [24]

Answer:

The answer to this question can be given as:

Normalization:

Normalization usually includes the division of a table into two or more tables as well as defining a relation between the table. It is also used to check the quality of the database design. In the normalization, we use three-level that are 1NF, 2NF, 3NF.

First Normal Form (1NF):

In the 1NF each table contains unique data. for example employee id.

Second Normal Form (2NF):

In the 2NF form, every field in a table that is not a determiner of another field's contents must itself be a component of the table's other fields.

Third Normal Form (3NF):

In the 3NF form, no duplication of information is allowed.

Explanation:

The explanation of the question can be given as:

Since all attribute values are single atomic, the given relation CAR_SALE is in 1NF.
Salesperson# → commission% …Given Thus, it is not completely dependent on the primary key {Car#, Salesperson#}. Hence, it is not in 2 NF.

The 2 NF decomposition:

CAR_SALE_1(Car#, Salesperson#, Date_sold, Discount_amt)

CAR_SALE_2(Salesperson#, Commission%)

The relationship in question is not in 3NF because the nature of a transitive dependence occurs
Discount_amt → Date_sold → (Car#, Salesperson#) . Thus, Date_sold is neither the key itself nor the Discount amt sub-set is a prime attribute.

The 3 NF decomposition :

CAR_SALES_1A(Car#, Salesperson#, Date_sold)

CAR_SALES_1B(Date_sold, Discount_amt)

CAR_SALE_3(Salesperson#, Commission%)

5 0

1 year ago

A patient asks her doctor to send a copy of her records to another medical office. However, the records are not transmitted beca

bezimeni [28]

This type of security failure is called WIN32K_SECURITY_FAILURE. This indicates a security failure was detected in win32k. According to a new report issued by Dark Reading, there are a number of key security failures that cybercriminals take advantage of.

5 0

2 years ago

Read 2 more answers

George is working with an image in Photoshop. He added a lot of effects to the image. He saved the first draft of the file. The

Alja [10]

Answer:

JPEG, PDF

Explanation:

3 0

2 years ago

Read 2 more answers

Explain why each of the following names does or does not seem like a good variable name to represent a state sales tax rate.

tatyana61 [14]

a. stateTaxRate - A good variable name because it represents what it holds, the state sales tax rate, without being too wordy. Also correctly capitalized in camelcase.

b. txRt - A bad variable name because while short and simple, it is too hard to understand what the variable represents.

c. t - A very bad variable name if you plan on using the variable often. Far too short and you will forget what it represents and is needed for.

d. stateSalesTaxRateValue - A bad variable name because it is just too wordy. Cutting it down to A's variable name is much more reasonable

e. state tax rate - A bad variable name and probably invalid because it has spaces in the name.

f. taxRate - A good variable name if there are no other tax calculations other than state tax rate. Otherwise you would confuse state vs local tax rate or something, making it a bad variable name.

g. 1TaxRate - A bad variable name because the number 1 has no reason being in the variable name. It doesn't add anything to the name.

h. moneyCharged - A bad variable name because it is not specific enough in explaining why the money is being charged and what for.

7 0

2 years ago