Java Core Classes and Threads

'delete' is not a keyword in Java, unlike in C++ where it is used for memory deallocation. Java does not expose manual memory management through keywords - it uses automatic garbage collection instead. 'delete' has no special meaning in Java syntax or standard libraries.

Black list validation is weak because attackers can bypass filters using character encoding variations like URL encoding, Unicode, or hex encoding. White list validation is more secure because it only allows known-good patterns. Hard coding (A) and POST method handling (C) aren't fundamental weaknesses, and black lists don't use regex patterns (D).

Blacklist validation is weak because attackers can easily bypass it using various character encoding techniques like URL encoding, Unicode variations, or hex encoding. Since blacklists try to block specific bad patterns, they inevitably miss novel attack vectors. Whitelist validation (allowing only known good patterns) is much more secure.

A marker interface is an interface with no methods or fields, serving only to mark a class for special handling (e.g., Serializable, Cloneable, Remote). It conveys metadata to the JVM or compiler through the interface's presence alone.

The dpNext() method is the standard RFT API call to advance the datapool cursor to the next row. Other options like dpMoveCursor(), dpNextRow(), or dpMoveNext() are not valid RFT methods.

JSF Validators are classes that implement the javax.faces.validator.Validator interface and validate the given input. The Validator interface defines a validate method that must be implemented. Note that it's an interface (implement), not an abstract class (extend), and the package is validator, not validate.

In Java's Thread class, suspend(), resume(), and stop() are final methods and therefore cannot be overridden by subclasses. These methods are also deprecated in modern Java. The destroy() method is not final, so it can technically be overridden, though it's also deprecated.

In Java, threads acquire locks at the object level using intrinsic locks (monitor locks). Each object has an associated monitor that threads can lock or unlock. Threads do not lock heap memory, classes themselves, or individual variables - they lock objects to achieve synchronization.

The wait(), notify(), and notifyAll() methods must be called from within a synchronized context (i.e., while holding the object's lock). Invoking these methods without acquiring the lock results in IllegalMonitorStateException at runtime.

sleep() and activeCount() are static methods of the Thread class - you call them directly on Thread.sleep() or Thread.activeCount(). join() is an instance method that you call on a specific thread object. 'none' is incorrect since join() is indeed not static.

wait(), notify(), and notifyAll() are defined in the Object class, not the Thread class - they're available on every object in Java for inter-thread communication. start() IS a method of Thread class that begins execution.

Thread defines three priority constants: MAX_PRIORITY (10), MIN_PRIORITY (1), and NORM_PRIORITY (5). LOW_PRIORITY doesn't exist - it's a distractor mixing 'LOW' with the correct constant name MIN_PRIORITY.

Black list validation is weak because attackers can bypass it using various character encoding techniques (URL encoding, Unicode, double encoding, etc.) to represent blocked characters in ways the filter doesn't recognize. Being hard-coded (A) doesn't make it weak. POST method handling (C) isn't specifically problematic for black lists. Black lists don't match good patterns (D) - they block bad ones.