Internet and Web

Adding web servers increases system availability (redundancy means if one fails, others continue serving), performance (load distribution across more servers), and reliability (redundancy reduces single points of failure). It does not inherently improve extensibility (ability to add features), maintainability (ease of modification), or manageability (ease of administration) - these would require architectural or process changes beyond just adding hardware.

The Sales user details page specifically displays a user's access configurations, including associated Sales Access Profiles and permissions. The Visibility page shows territory associations, not access information.

The GET method sends form input data through the URL query string, visible in the browser address bar. POST sends data in the HTTP request body and doesn't expose parameters in the URL. Therefore, GET is the method that sends input via URL.

JavaScript has three built-in popup boxes: Alert (displays a message), Confirm (asks for OK/Cancel confirmation), and Prompt (requests user input). Radio buttons are form input elements, not popup boxes.

The standard JavaScript method for opening a new browser window or tab is window.open(). Other options like window.launch() or popUp() are not built-in JavaScript window methods, and window.close() is used to close an existing window.

In a GET request, the query string (the key=value pairs after the ? in the URL) is logged by the web server in access logs. Hidden tags are in the HTML body and not sent separately. Headers are logged but are server metadata, not request content. Cookies are sent in headers.

Flex breaks free of the traditional web's link-and-page metaphor by enabling single-page applications with dynamic content without full page refreshes. It does NOT have slow page refreshes (that's traditional web) or progressively loading content (that's progressive enhancement). Option A correctly describes Flex's architectural advantage.

In a multitiered application architecture, the browser runs on the client side and handles user interface presentation. This is known as the presentation tier or first tier. The other tiers (application logic tier and data tier) typically run on servers.

To solve this question, the user needs to know what a GET request is and how it works.

When a client (usually a web browser) sends a GET request to a web server, the server logs various information about the request. This information includes the requested resource (such as a webpage or image), the client's IP address, and other details.

Now, let's go through each option and explain why it is right or wrong:

A. Hidden tags: This option is incorrect because hidden tags are not part of a GET request. Hidden tags are used in HTML forms to send data to the server using the POST method, not the GET method.

B. Query Strings: This option is correct. Query strings are part of a GET request and allow the client to send additional information to the server. Query strings are appended to the end of the requested URL and are separated by a question mark (?). For example, in the URL "http://example.com/search?q=term", the query string is "q=term".

C. Header: This option is partially correct. The header of a GET request is logged by the server and contains information such as the client's user agent, accepted languages, and other details. However, this option is not the only part of a GET request that is logged.

D. Cookies: This option is incorrect because cookies are not part of a GET request. Cookies are used to store information on the client's side and can be sent to the server in subsequent requests, but they are not part of the initial GET request.

Therefore, the correct answer is:

The Answer is: B. Query Strings

Authorization checks prevent unauthorized access by verifying permissions for each request. Obscurity (B) is not real security since attackers can discover file names through other means. File organization (C) and ACLs (D) don't stop direct URL manipulation attacks.

CSRF tokens prevent Cross Site Request Forgery by ensuring requests are genuinely from the intended user. They do not prevent XSS (A) or XST (C) which are different vulnerability classes.

CSRF tokens prevent Cross Site Request Forgery by ensuring that requests come from the legitimate application, not from a malicious site. The token is a secret value that attackers cannot include in their forged requests. Options A (XSS) and C (XST) are different vulnerability types.

CSRF tokens prevent Cross-Site Request Forgery by including a secret, unpredictable token in state-changing requests. Attackers cannot forge valid requests without knowing this token. CSRF is distinct from XSS (script injection) and XST (HTTP TRACE method abuse).

Multimedia elements should be utilized sparingly to reinforce the website's goals and content. Overusing them degrades loading performance and distracts users, while completely avoiding them limits engagement where media would otherwise be beneficial to the user experience.

The World Wide Web Consortium (W3C) is the international organization that develops web standards including HTML, CSS, and HTTP. Mozilla and Microsoft are browser vendors who implement these standards, not standards bodies.