Java Quiz — 7 Free Questions

Question 1

What is the purpose of the "@Deprecated" annotation applied to a Java method?

Question 2

What is the purpose of an "abstract" method declared inside an abstract class?

Question 3

What does JDBC stand for, and what is its purpose in Java?

Question 4

What ordering guarantee, if any, does a standard HashMap provide over its entries?

Question 5

What is the purpose of the "package-private" (default) access level applied to a class member with no explicit modifier?

Question 6

What problem does the java.util.Optional class primarily help address?

Question 7

What is the purpose of the java.time package, introduced in Java 8 to replace the older Date and Calendar classes?

📚 All Quizzes

Browse every category and see the full list of quizzes on BriskQuiz

→

About Java

James Gosling led the small team at Sun Microsystems that built what would become Java, originally under the internal codename "Oak" after a tree outside Gosling's office. When Sun released it publicly in 1995, its pitch was "write once, run anywhere": code compiled down to bytecode that ran on the Java Virtual Machine instead of directly on one operating system, so the exact same program could run unmodified on wildly different hardware.

That single idea reshaped how software got built for the next three decades. Java also introduced automatic garbage collection to a mainstream audience at a moment when most competing languages still required developers to manage memory by hand, removing an entire category of common, hard-to-debug crashes in the process.

Java went on to become the backbone of two very different worlds at once. It's the language Android apps were originally built on, giving it a foothold on essentially every smartphone that isn't an iPhone, and it's also the language that still runs an enormous share of the world's banking, insurance, and government back-end systems, often through the Spring framework that grew up specifically to make enterprise Java development less painful.

The JVM itself became a platform in its own right too. Its combination of speed, portability, and maturity made it an attractive foundation for entirely new languages, and Kotlin, Scala, and Clojure all now run on the same virtual machine Java pioneered, letting them tap into decades of tooling and libraries built for Java without starting from zero.

Oracle's acquisition of Sun Microsystems in 2010 brought Java under new ownership, and the language shifted to a faster, more predictable release cadence with regular long-term-support versions that enterprises could safely standardize on for years at a time.

Despite approaching thirty years old, Java consistently lands near the top of language-popularity rankings, and its sheer footprint in existing, still very much actively maintained systems means demand for developers who genuinely understand it has never really gone away, even as newer languages get more of the hype.

Android's relationship with Java has shifted in recent years, with Google now officially recommending Kotlin, a newer JVM language, as the preferred choice for new Android apps. Even so, Java remains deeply embedded in the platform's history and in millions of lines of existing Android code that isn't going anywhere soon, and Kotlin itself was specifically designed to interoperate seamlessly with existing Java code rather than replace it outright.

Java's release cadence has also sped up considerably since Oracle took over its stewardship, moving from infrequent, feature-packed releases every few years to a predictable schedule of smaller releases every six months, with select versions designated as long-term-support editions that large companies can safely standardize on without needing to constantly chase the newest release.

Java's official mascot, Duke, a friendly waving cartoon character, has been part of the language's branding since its earliest public unveiling in 1995, and remains one of the more recognizable mascots in the programming world, predating similar friendly mascots that later languages like Go would adopt for the exact same reason: making a technical product feel a little more approachable.