Mixed Programming Languages Quiz

To retrieve values from an HTML form, use request.getParameter() on the HttpServletRequest object. There is no setParameter() method on request, and response is for sending data back to the client, not receiving it.

Static variables are shared only within a single JVM instance. Each server runs its own JVM with its own memory space, so static variables are not shared across different servers. Each servlet instance on each server has its own separate copy of the static variable.

In Java Servlets, user authentication information is accessed through the HttpServletRequest object using getRemoteUser() for basic authentication or getUserPrincipal() for form-based authentication. The HttpServletRequest interface provides methods to retrieve authentication data, not HTTPRequest, HTTPResponse, or setUserName methods.

In MVC architecture, the controller acts as the intermediary between the view (presentation layer) and model (business logic/data). It processes user input, interacts with the model, and selects the appropriate view for rendering. The controller is the glue that coordinates view and model interactions.

The UNDO_POLICY=REQUIRED option in SAS SQL ensures that if any rows in an INSERT or UPDATE operation fail to meet the specified integrity constraint criteria, the entire operation is rolled back and the table is restored to its original state before the operation began. This provides transactional integrity by preventing partial updates. Option C correctly describes this behavior.

The query performs a Cartesian product (cross join) of tables ONE and TWO because no WHERE clause joins them. Table ONE has 2 rows (X=1,Y=2 and X=2,Y=3) and Table TWO has 3 rows (X=2,Z=5, X=3,Z=6, X=4,Z=9). The result is 2 × 3 = 6 rows, combining each row from ONE with each row from TWO. Option A shows all 6 rows correctly.

The query performs an inner join on column b between tables ONE and TWO. Matching rows: both have (a,1), (b,2), (c,.) with NULL/SAS missing values. The row (d,4) appears in both tables. Row (e,.) and (f,.) in table TWO don't have matches in ONE. The inner join returns all matched rows including NULL matches on the join column. Option B correctly shows all 6 matched rows.

The MERGE statement in SAS combines datasets by matching the BY variable (flight). FLTSUPER has 6 flights (145,145,150,150,155,157) and FLTDEST has 5 flights (145,145,150,150,165). MERGE matches all occurrences: 145 matches both rows, 150 matches both rows, while 155, 157 appear only in FLTSUPER, and 165 appears only in FLTDEST. The result contains all observations from both datasets. Option D shows all 7 rows correctly.

The SQL query performs an inner join between fltsuper and fltdest on Flight. Flight 145 appears twice in both tables (2×2=4 combinations), Flight 150 appears twice in both tables (2×2=4 combinations). The other flights (155, 157 in fltsuper; 165 in fltdest) have no matches and are excluded from the inner join result. The output has 8 rows total. Option A correctly shows the pattern, though it appears truncated at the end.

In SAS SQL set operations (UNION, INTERSECT, EXCEPT) without keywords like ALL or CORR, columns are matched by position (ordinal) not by name. The columns must have compatible data types but need not have the same name. Column names in the result come from the first table. Therefore, the statement that 'To be overlaid, columns must have the same name' is FALSE, making option C the correct answer.

Option B correctly uses CASE with WHEN clauses (not IF) and multiplies pointsearned by the appropriate factor (1.5 for <10000 miles, 2 for >=10000 miles). Options A, C, and D incorrectly use IF instead of WHEN in the CASE statement syntax. Options C and D also incorrectly reference pointsearned again inside the CASE expression, which would cause double multiplication.

Option C uses the correct PROC SQL syntax DESCRIBE TABLE to display table structure in the SAS log. Option A incorrectly combines DESCRIBE with a SELECT statement. Option B uses CONTENTS which is valid for dictionaries but not the correct syntax for tables. Option D incorrectly uses DESCRIBE with a wildcard.

Option B is correct: the UNIQUE keyword in CREATE INDEX prevents duplicate values in the indexed column. Option A (KEY) is not a valid keyword for enforcing uniqueness. Option C (NODUPS) is not valid SAS syntax. Option D (NODUPKEY) is a SAS dataset option, not a CREATE INDEX keyword.

LCID (Locale Identifier) is the Session object property used to set the local identifier for locale-specific formatting and cultural conventions. View State, key, and Session Id serve different purposes in session management.

ASP.NET allows multiple master pages (any number) for different layouts, but only one site map file (web.sitemap) per website to define the navigation structure hierarchy.

In .NET, classes declared at the namespace level can only use public or internal access modifiers. The Protected modifier is only valid for class members (nested classes, methods, properties), not for top-level class declarations.

Classes declared directly within a namespace cannot be declared as private in .NET. Namespace-level classes can only be public or internal. The Private modifier is only valid for nested class declarations inside another class.

.NET supports both Custom Attributes (user-defined) and Predefined Attributes (built-in like [Serializable], [Obsolete]). Functional Attributes do not exist as a category in .NET.

When you call a static method on a null reference (x.m() where x is null and m is static), Java doesn't throw NullPointerException because static methods are bound to the class, not the instance. The other options are false: null instanceof Object is false, and passing null to anonymous inner class constructor is generally problematic.

All three statements describe why Java avoids global variables: they break referential transparency, reduce cohesion, and limit reusability by tying code to a single instance. Since each individual reason is valid, the combined choice “All of above” correctly captures the rationale.