General Technology Concepts Quiz

A .class file contains compiled Java bytecode for a single class. Multiple class files work together (along with libraries) to run a complete Java application.

JAR (Java Archive) bundles multiple class files and resources into one compressed file for efficient distribution - only one HTTP request needed instead of many.

Java enforces strict rules (strong typing, no pointers, garbage collection, OOP structure) that constrain how you write code - less freedom than C/C++ but safer and more maintainable.

An applet is a Java program designed to be transmitted over the Internet and executed within a web browser. It runs in a sandboxed environment for security. Options B and C describe other types of software components, while D incorrectly restricts applets to only graphics.

When you extend a class using inheritance, you create a subclass (derived class) that inherits features from the superclass. The subclass is a specialized version of the parent class. Options B, C, and D describe unrelated concepts - extension is about inheritance, not instances or memory allocation.

HotJava was the first web browser written in Java, developed by Sun Microsystems in 1995. It demonstrated Java's capability for building complex applications. Options B, C, and D refer to other products or concepts - Symantec Cafe was an IDE, JIT compilation is a compiler optimization, not a browser.

In Apache Axis, incoming messages on the server side flow through three layers: Transport (HTTP, SMTP, etc. listeners receive the request) → Global (common handlers for all services process security, logging) → Service (specific service handlers execute business logic). This layered architecture allows cross-cutting concerns to be handled before service-specific processing.

In Apache Axis, the client-side message path flows from the Service (where the application invokes the service), through Global handlers (which process all messages), and finally to the Transport layer (which handles the actual HTTP/SOAP transmission). This is the correct sequence for outbound messages on the client side.

The Axis Message Model subsystem encompasses multiple components: the SOAP Message Model defines the structure of SOAP messages, Message Elements represent the parts of messages (headers, body, faults), and Deserialization handles converting XML to Java objects. All three are integral parts of how Axis manages message processing.

Apache Axis architecture consists of three main architectural components: the Message Path on the Server (how messages flow through server-side processing), Handlers and the Message Path in Axis (the processing chain), and the Message Path on the Client (how messages flow through client-side processing). All three are fundamental architectural elements.

In the Axis Message Flow subsystem, the Handler is known as the pivot point of the sequence. Handlers are the processing components that intercept and transform messages as they flow through the chain, acting as the central pivot around which message processing revolves. The message itself flows through, service is the endpoint, and chain is the collection.

Active Directory can assign applications to both users and computers (forced installation), and can publish applications to users (add to Add/Remove Programs list). However, it CANNOT publish applications to computers because publishing requires user action to choose installation, and computers don't make such choices.

Active Directory has two forest-wide Single Master Operations (FSMO roles): Schema Master (controls schema updates) and Domain Naming Master (controls adding/removing domains). The other two (RID Master and Infrastructure Master) are domain-specific roles that exist in each domain separately.

All listed options (User, Group, Organizational Unit, Computer) ARE valid Active Directory objects. Since the question asks which is 'not' valid and all options A-D are valid objects, 'None of the above' (E) is the correct answer because there is no invalid object in the list.

The Active Directory Installation Wizard (dcpromo) requires all the listed information: the domain name for the forest/domain being created, local admin password for authentication, NetBIOS name for backward compatibility, and DNS configuration since AD requires DNS. All of these are prerequisites.

Security principals are AD objects that can authenticate and receive permissions: Users, Security Groups, and Computers. Distribution Groups are NOT security principals - they're used only for email distribution in Exchange and cannot be assigned permissions or authenticate.

Windows Server 2008 can function in all three server roles: Stand-alone server (workgroup), Member server (domain-joined but not a DC), and Domain Controller (hosts AD). All are valid roles depending on the network topology and requirements.

Active Directory trust relationships support all combinations: one-way or two-way direction, and transitive or non-transitive characteristics. These can be combined in various ways to create complex trust topologies between forests and domains.

OU structure should be designed based on administrative needs: how you want to organize the domain, how you need to delegate permissions, and how you plan to apply Group Policies. Network infrastructure (physical topology, IP addressing, etc.) should have minimal influence on OU design.

The .msi (Microsoft Installer) extension is the standard file format for Windows Installer setup packages. These files contain installation information and are used by the Windows Installer service to install applications. .mst files are transform files used to modify installations, .zap is for Windows Installer patches, and .aas is not a standard Windows Installer extension.