Tuesday, 11 April 2017

O Level Solve Paper Jan 16

O Level Solved Paper

January, 2016 M4.1-R4: APPLICATION OF .NET TECHNOLOGY

Solved Paper

Objective Type Answer


1.1 : B
1.2 : C
1.3: D
1.4 : A
Explanation : Supports all classes in the .NET Framework class hierarchy and provides low-level services to derived classes. This is the ultimate base class of all classes in the .NET Framework; it is the root of the type hierarchy.
1.5 : D
Explanation : The IHttpHandlerFactory interface creates and manages HTTP handlers for processing requests. Therefore, you can create a class that implements the IHttpHandlerFactory interface, and then use that class as an HTTP handler.

1.6: D
Explanation :Java is not compliant with CLS defined in .NET.

1.7:  A
Explanation :

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs"Inherits="_Default" %>

The ASP.NET page framework supports an automatic way to associate page events and methods. If the AutoEventWireup attribute of the Page directive is set to true, the page framework calls page events automatically, specifically the Page_Init and Page_Load methods. In that case, no explicit Handles clause or delegate is needed.
  • AutoEventWireup is an attribute in Page directive. 
  • AutoEventWireup is a Boolean attribute that indicates whether the ASP.NET pages events are auto-wired.
  • AutoEventWireup will have a value true or false. By default it is true.

There is no event or method associated with Page_Load. Those events whose inline event is not there but that should be executed, for that purposed AutoEventWireup="true".

1.8 : C
1.9:  B
Explanation : Gets a value that indicates whether the page is being rendered for the first time or is being loaded in response to a postback.

1.10 : A

True/False

2.1 : T
Explanation : 
Yes, we can run an asp.net application without the WEB.CONFIG file. 
If we are not setting any configuration in WEB.CONFIG file then it will take MACHINE.CONFIG file for default configurations. This config file will automatically installed when your application getting executed. 
i.e MACHINE.CONFIG file contains defaults settings for all the asp.net web applications.
Because all the configuration settings will be available under MACHINE.CONFIG file by default these settings will be applied to all asp.net applications. 

2.2 : T
2.3 T
2.4 F
Explanation :  The machine configuration file, Machine.config, contains settings that apply to an entire computer. This file is located in the %runtime install path%\Config directory. Machine.config contains configuration settings for machine-wide assembly binding, built-in remoting channels, and ASP.NET.

The configuration system first looks in the machine configuration file for the appSettings Element (General Settings Schema) and other configuration sections that a developer might define. It then looks in the application configuration file. To keep the machine configuration file manageable, it is best to put these settings in the application configuration file. However, putting the settings in the machine configuration file can make your system more maintainable. For example, if you have a third-party component that both your client and server application uses, it is easier to put the settings for that component in one place. In this case, the machine configuration file is the appropriate place for the settings, so you don't have the same settings in two different files.

2.5 : T
2.6 : T 
2.7: T
2.8 : F
2.9 T 
Explanation :   Because function can return a value but procedure has not returning capacity

2.10 : T

3. Match The Column

3.1 : (E) Page Class
3.2 : (K) Inproc
3.3: (M) Class Declaration 
3.4: (A) Managed Code
3.5 : (J) Containership

           Explanation :

This shows relationship between two classes. When a class have object of another class then this type of relationship called containership.
Class Test
{
--------
--------
}
Class Best
{
--------
--------
}
Class Rest
{
   public Rest()
   {
        Test ob1=new Test();
        Best  ob2=new Best();
   }
------
}

3.6 : (C)
3.7 : (I)
3.8 : (B)
3.9 (L)
3.10 (G)

4 Fill in the Blank

4.1 :  (F) Serialization
4.2 :  (J) sealed 
4.3 :  (B.) Reflection 
4.4 :   (K.) Dispose()   
4.5 :   (D) Ctype 
4.6  :  (H) throw ex
4.7 : 
4.8 :   (L) structure ,classes    
4.9 :   (I) System.Globalization
4.10 :  (C) Panels