A junior developer is programming a combat system for an RPG. They decide to manage player status effects using standard String variables, writing code like player.inflictStatus("Burned"); and checking it later with if (status.equals("burned")) . According to the "Pre-class activities: enumeration" reading, what is the primary architectural danger of this approach, and how does a Java enum resolve it?

Question

A junior developer is programming a combat system for an RPG. They decide to manage player status effects using standard String variables, writing code like  player.inflictStatus("Burned");  and checking it later with if  (status.equals("burned")) . According to the "Pre-class activities: enumeration" reading, what is the primary architectural danger of this approach, and how does a Java enum resolve it?

Answer

Strings are dynamically typed; enums bypass garbage collection to improve overall performance.

Answer

Strings are forbidden in switch statements; enums are the only valid type for conditional branching.

Answer

Strings consume excessive system memory; enums compress data into integers to speed up execution.

Answer

Strings violate encapsulation principles; enums automatically apply private modifiers to their values.

Answer

Strings cause silent runtime logic bugs for typos; enums turn these into loud compile-time errors.

Crowdly

A junior developer is programming a combat system for an RPG. They decide to man...

Want instant access to all verified answers on learning.monash.edu?