web technology Online Quiz - 198

IBM Deep Blue was a chess-playing computer, not a cloud computing platform. Google 101 appears to be an incorrect option (possibly meant to be Google Cloud Platform), Microsoft Azure and Amazon EC2 are both major cloud platforms. The question has quality issues with the options.

Cloud computing offers scalable, on-demand resources that replace the need for physical corporate data centers, high-end local PC hardware for processing, and the manual management of expensive software upgrades, as these are handled by the provider.

Security is consistently cited as the primary concern for organizations moving to cloud computing, as it involves placing sensitive data and infrastructure under the control of a third-party provider.

CLR stands for Common Language Runtime. It is the virtual machine component of Microsoft's .NET framework that manages the execution of .NET programs and provides services like memory management and security.

Web.config is the standard XML-based configuration file used in ASP.NET applications to manage settings like connection strings, authentication, and custom application settings. App.config is used for Windows desktop applications.

In ASP.NET, the OnClientClick property allows you to run JavaScript before the postback. If the JavaScript function returns 'false', the server-side click event (postback) is cancelled.

In C#, const fields are compile-time constants that must be initialized at declaration and cannot change. readonly fields can only be assigned at declaration or in a constructor, but their values can vary between instances. They serve different purposes.

In ASP.NET, the EnableViewState attribute of a server control determines whether the control maintains its view state across multiple requests. The ID, RunAt, and Name attributes serve other purposes such as identification and server-side processing.

The JOIN keyword in SQL is used to combine and select rows from two or more database tables based on a related column between them. Data deletion and updates are handled by DELETE and UPDATE statements respectively.

A thin-client application is one where the bulk of the processing occurs on the server. The client is primarily responsible for the user interface and passing data to the server-side components (like enterprise beans) for logic execution.

PUT, HEAD, and DELETE are all fully valid HTTP 1.1 methods. Therefore, the option stating 'All of the above are valid HTTP 1.1 methods' is correct.

HttpSession, ServletRequest, and ServletContext all define getAttribute() and setAttribute() methods to manage attributes within their respective scopes. ServletConfig only supports getInitParameter() and does not have attribute methods.

In J2EE 1.4 API, HttpSessionBindingEvent exists for session attribute binding/unbinding, but HttpSessionAttributeEvent does not exist. HttpSessionEvent, ServletRequestEvent, and ServletContextAttributeEvent are all valid listener event types in the specification.

getSession() (no-arg) and getSession(true) both create a new session if one doesn't exist. getSession(false) returns null if no session exists, without creating one. The createSession() methods do not exist in the HTTPServletRequest API.

sendRedirect(String url) is the correct method on HttpServletResponse to redirect the client to a different URL. This sends a temporary redirect (HTTP 302) to the browser. getRequestDispatcher() is for server-side forwards, not redirects.

In JSP, 'application' is a valid implicit variable representing the ServletContext. Other implicit objects include request, response, session, out, pageContext, config, and page. 'stream', 'context', and 'listener' are not standard JSP implicit variables.

JSP lifecycle includes jspInit() for initialization and jspDestroy() for cleanup, both of which can be overridden by developers. The _jspService() method is generated by the container and cannot be overridden - it's where your JSP code ultimately executes.

Valid JSP directives are page, taglib, and include. 'import' is not a directive itself - it's an attribute of the page directive used for importing Java classes. Directives always start with <%@ and end with %>.

The jsp:forward standard action uses the 'page' attribute to specify the target resource, not 'file'. The correct syntax is <jsp:forward page="view.jsp" />. There is no 'dispatch' standard action in JSP.

A tag is considered empty only if it has no body content. Option D contains a scriptlet (<%=...%>) which produces output, giving it body content. Options A, B, and C are truly empty - A uses self-closing syntax, B has no content between tags, and C uses jsp:attribute for setting attributes.