98-372 Question #11: Real Exam Question with Answer & Explanation

Question

Options

• AIt guarantees the uniqueness of a name.
• BIt ensures that subsequent versions cannot be produced.
• CIt describes the identity permission for strong names.
• DIt provides versioning and naming protection.

Explanation

A strong-named assembly is a commonly deployed element in a .NET application. Following are the benefits of a strong-named assembly: A strong-named assembly guarantees the uniqueness of a name, as it relies on the unique key pairs i.e. private and public keys. An assembly name cannot be generated with the same name, as each time the assembly generates a private key with a different name. A strong-named assembly ensures that subsequent versions cannot be produced, as the version of an assembly is loaded from the same publisher into which the assembly version was created when the application was built. A strong-named assembly provides a strong integrity check. It guarantees that the contents of an assembly have not been modified since it was built. It is usually identified by a digital signature and a supporting certificate. Answer: C and D are incorrect. The StrongNameIdentityPermission class is used to describe the identity permission for strong names. In order to have a strong name for an assembly, the code should be signed by a key pair. .Net provides the utility, sn.exe, to generate a key pair. This class provides versioning and naming protection by verifying that the calling code is in a particular strong-named code assembly. It also defines strong-name requirements for access to the public members of a type. The StrongNameIdentityPermissionAttribute class can be used to define strong-name requirements at the assembly level.

No community discussion yet for this question.