NestJS Risk Assessment & Management 3

Question 1

Which NestJS mechanism is best suited to log all unhandled exceptions centrally, supporting post-incident risk analysis?

Accepted Answer

A global ExceptionFilter registered with useGlobalFilters()

Answer

A global ExceptionFilter catches every unhandled exception across all routes, making it the correct place to log errors and trigger alerts.

Question 2

What risk does enabling CORS with origin: '*' introduce in a NestJS REST API that uses cookie-based authentication?

Accepted Answer

Any website can make credentialed cross-origin requests, enabling CSRF attacks

Answer

Wildcard CORS with credentials allows any origin to send authenticated requests, undermining same-origin protections and enabling CSRF.

Question 3

In NestJS microservices, what risk does using a message broker without message validation introduce?

Accepted Answer

Malformed or malicious payloads can crash consumers or corrupt data

Answer

Without schema validation on consumed messages, a bad payload can trigger unhandled exceptions in downstream microservices or insert corrupt data.

Question 4

Which NestJS-compatible tool helps assess dependency vulnerabilities as part of a supply-chain risk management process?

Accepted Answer

npm audit or Snyk integrated into CI/CD pipelines

Answer

npm audit and Snyk scan installed packages for known CVEs, enabling teams to patch vulnerable dependencies before deployment.

Question 5

A NestJS application processes file uploads. What risk is introduced if uploaded file types and sizes are not validated?

Accepted Answer

Attackers can upload malicious executables or exhaust disk/memory with oversized files

Answer

Without file-type and size checks, attackers can upload malware or trigger denial-of-service by sending excessively large files.

NestJS Practice Test