ASP.NET Fundamentals

Custom controls in ASP.NET typically derive from System.Web.UI.WebControls.WebControl (for UI-heavy controls) or System.Web.UI.Control (for logic-heavy controls). The option provided (2625) appears to be a specific or slightly mislabeled hierarchy, but WebControl is the standard base.

Classic ASP was an interpreted scripting language (VBScript/JScript). ASP.NET introduced a compiled model where code is separated into code-behind files or script blocks that are compiled into DLLs (Intermediate Language), providing significantly better performance and type safety.

Response.Output.Write() provides formatted output capabilities using String.Format-style syntax, while Response.Write() only writes raw strings. Response.Output.Write() allows you to write formatted output with parameters like Response.Output.Write("Hello {0}", name), making it more flexible for dynamic content generation. The other options (flush, buffer, stream) are not the key differences.

Global.asax is the ASP.NET application file that handles application-level and session-level events. It contains event handlers like Application_Start, Application_End, Session_Start, and Session_End, allowing developers to respond to key application lifecycle events.

A system can have multiple machine.config files if multiple versions of the .NET Framework are installed. Each version (e.g., v2.0, v4.0) has its own configuration directory and its own machine.config file to manage settings specific to that runtime version.

Web user controls in ASP.NET use the .ascx file extension. The .aspx extension is for web forms pages, and .asmx is for XML web services. User controls are reusable components that can be embedded in multiple pages.

IsPostBack is a property of the System.Web.UI.Page class that returns a boolean value indicating whether the page is being loaded in response to a client postback or if it is being loaded for the first time. It is a property, not a method.

In ASP.NET Web Forms, only one server-side form (runat="server") is allowed per page. This is because the Web Forms model relies on a single postback mechanism to manage state via ViewState. Multiple client-side HTML forms are possible, but only one server form.

ASP.NET supports multiple state management techniques across different scopes. Session objects store user-specific data, Application objects store application-wide data shared across all users, and ViewState maintains page-level state across postbacks.

The LCID (Locale Identifier) property of the Session object is used to set or get the identifier that specifies the location and language for the current session, affecting date, time, and currency formatting. SessionId is a unique string for the session, not a locale identifier.

ASP.NET supports both output caching (caching the entire page or portions of it using @OutputCache directive) and data caching (caching data objects programmatically using the Cache object). Option C correctly identifies that both types are supported.

By default, ASP.NET stores session data in the InProcess mode, which keeps session data in the memory of the ASP.NET worker process. StateServer and SQL Server are alternative storage modes that need to be explicitly configured in web.config for web farm scenarios or when persistence across process restarts is needed.

ASP.NET uses an event-driven processing model where page lifecycle and control events are raised in a specific sequence. Developers write code to handle these events (like Page_Load, Button_Click, Init, etc.) rather than following linear or top-down execution.