Can you sit the TypeScript Certification today?

What does `declare module "vendor-analytics" { export function track(event: string): void; }` accomplish?

• AIt implements the vendor-analytics module's actual runtime behaviour
• BIt hand-declares the shape of an untyped third-party module, letting TypeScript check code that imports from it, without providing or verifying against a real implementation
• CIt renames the vendor-analytics package
• DIt is only valid syntax inside a .ts file, never a .d.ts file

What is the key distinction between a generic type parameter and the type any, as a way of writing flexible, reusable code?

• Aany is checked more strictly than a generic type parameter
• BThere is no real distinction; they solve the identical problem
• Cany discards checking entirely and loses the relationship between input and output; a generic type parameter preserves that relationship, still fully checked for whatever concrete type it resolves to at each call
• DGenerics can only be used with primitive types, unlike any

What is a realistic risk of having both a package's own bundled types and a separately installed @types/package-name for the same package?

• AThere is no risk at all; this configuration is always perfectly safe
• BConflicting or duplicate declarations, since the package's own types and the separately installed @types package can disagree
• CIt causes an immediate runtime crash on import
• DIt silently disables type checking for the whole project

What is a literal type union like `"left" | "right" | "up" | "down"` stricter about than the plain type string?

• ANothing — they behave identically
• BIt only allows those four exact values, rejecting any other string (including a typo) that plain string would silently accept
• CIt only allows numbers
• DIt disallows all four listed values

Given `let value: any = fetchSomething(); value.whatever.deeply.nested();`, what happens at compile time?

• AIt only compiles if whatever actually exists at runtime
• BIt requires an explicit type assertion first
• CIt errors immediately, since whatever isn't a known property
• DIt compiles without any error at all, no matter how implausible the chain is