Rapid-fire questions an interviewer asks around OOP & Testbench Puzzles. Answer out loud, then check yourself.
Answer: Print `%p` (or object IDs) for the nested handles in source and clone before and after one controlled mutation. If identities match and both values move together, the clone path is shallow at that nesting point.
Trap: Inspecting only top-level object handles and concluding clone ownership is correct.
Answer: Because framework code often stores objects/components in base-typed handles. If the base declaration is non-virtual or signatures do not match for override, calls bind to base implementation regardless of runtime type.
Trap: Believing method-name match in derived class automatically guarantees polymorphic dispatch.
Answer: Place per-specialization static members inside the parameterized class, and place global static state in package scope or a non-parameterized base class. Validate by constructing at least two different specializations and checking both counters.
Trap: Keeping both statics inside `foo#(T)` and expecting one of them to be global across all `T`.
Answer: Resolve each `create()` against its full path (`{context}.{name}`): a matching instance override beats any type override, and among several matching instance overrides the first one registered wins (there is no specificity ranking). With no instance match, the type override applies. Then remember direct `new()` bypasses all of it.
Trap: Believing an exact path beats a wildcard, omitting the leaf name from the instance path, and forgetting `create` vs `new`.