70-450 · Question #41
You are a professional level SQL Sever 2008 Database Administrator. A thirdparty database application will be deployed to the instance. Stored procedures are utilized by the application, and the…
The correct answer is B. The peverify.exe PEVerify tool should be utilized to confirm whether the type-safety. This is a vague question, but we can eliminate three answers just based on context. PEVERIFY is used to determine if type-safety requirements are met. From the first part of the guide, we know that read-only static fields are the only ones permitted, so that excludes A) and C)…
Question
You are a professional level SQL Sever 2008 Database Administrator. A thirdparty database application will be deployed to the instance. Stored procedures are utilized by the application, and the procedures are developed by utilizing SQL CLR integration. You should set the application to have the EXTERNAL_ACCESS code access security setting enabled. Since you are the technical support of the company, you should deploy the application to the instance with no loss of functionality. Which action will you perform first?
Options
- AReadwrite non-static fields in the code should be replaced with static fields.
- BThe peverify.exe PEVerify tool should be utilized to confirm whether the type-safety
- CRead-only static fields in the code should be replaced with readwrite static fields.
- DThe regasm.exe assembly registration tool should be utilized to have the assembly
How the community answered
(37 responses)- A3% (1)
- B81% (30)
- C11% (4)
- D5% (2)
Explanation
This is a vague question, but we can eliminate three answers just based on context. PEVERIFY is used to determine if type-safety requirements are met. From the first part of the guide, we know that read-only static fields are the only ones permitted, so that excludes A) and C) from being acceptable answers. REGASM creates registry entries for COM functionality and isn't related here. ----------------------------------- All EXTEFINAL_ACCESS assemblies must meet the following criteria: - Static fields are not used to store information. Read-only static fields are allowed. - PEVerify test is passed. The PE.'erify tool {peverityexe), which checks that the MSIL code and associated metadata meet type safety requirements, is provided with the .NET Framework - Synchronization, for example with the SynchronizationAttribute class, is not used. - Finalizer methods are not used. The following custom attributes are disallowed in EXTERNAL_ACCESS assemblies: - System.ContextStaticAttribute - System.l\llTAThreadAttribute - System.Fiuntime.CompiIerServices.l.-1ethodImplAttribute - System.Runtime.CompiIerServicesCompilationHe|axationsAttribute - System.Ftuntime.Flemoting.Contexts.ContextAttribute - System.Runtime.Remotingflontexts.Synchronizationitiittribute - System.Runtime.|nteropServices.DI||mportAttribute - System.Security.Permissions.CodeAccessSecurityAttribute - System.Security.SuppressUnmanagedCodeSecurityAttribute - System.Security.Unverifiab|eCodeAttribute - System.STAThreadAttribute - System,ThreadStaticAttribute
Topics
Community Discussion
No community discussion yet for this question.