Configuration namespaces in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of accessing a nested configuration namespace?

Given a NestJS configuration service with namespaces, what will be the output of the following code?

NestJS

const config = new ConfigService({ database: { host: 'localhost', port: 5432 } });
const host = config.get('database.host');
console.log(host);

A undefined

B "database.host"

C "localhost"

D Throws an error

💡 Hint

Think about how nested keys are accessed in configuration namespaces.

The get method supports dot notation to access nested properties. So database.host returns the string "localhost".

📝 Syntax

intermediate

Which option correctly defines a configuration namespace in NestJS?

Choose the correct way to define a configuration namespace using registerAs in NestJS.

A registerAs('database', { host: 'localhost', port: 5432 });

B export const database = registerAs('database', () => ({ host: 'localhost', port: 5432 }));

C export const database = registerAs(() => ({ host: 'localhost', port: 5432 }));

D export default registerAs('database', () => ({ host: 'localhost', port: 5432 }));

💡 Hint

Remember that registerAs requires a name and a function returning the config object.

Option B correctly exports a constant assigned to registerAs with a name and a function returning the config object. Option B uses default export which is not typical. Option B misses the name argument. Option B passes an object instead of a function.

❓ state_output

advanced

What is the value of a nested config key after merging multiple namespaces?

Consider two configuration namespaces merged in NestJS. What is the value of app.port after merging?

NestJS

const appConfig = registerAs('app', () => ({ port: 3000, debug: true }));
const overrideConfig = registerAs('app', () => ({ port: 4000 }));

const configService = new ConfigService({
  ...appConfig(),
  ...overrideConfig()
});

const port = configService.get('port');
console.log(port);

A 4000

B 3000

C undefined

D Throws an error

💡 Hint

Think about how object spread works when merging objects with overlapping keys.

The second object overrideConfig() overwrites the port key from the first. So the final port is 4000.

🔧 Debug

advanced

Why does accessing a nested config key return undefined?

Given this code, why does config.get('database.password') return undefined?

NestJS

const config = new ConfigService({ database: { user: 'admin' } });
const password = config.get('database.password');
console.log(password);

A Because the config object is empty

B Because dot notation is not supported in get method

C Because ConfigService requires explicit schema for nested keys

D Because 'password' key does not exist in the 'database' namespace

💡 Hint

Check if the key you are accessing exists in the config object.

The password key is missing from the database object, so accessing it returns undefined. Dot notation is supported, and the config object is not empty.

🧠 Conceptual

expert

Which statement best describes configuration namespaces in NestJS?

Choose the most accurate description of how configuration namespaces work in NestJS.

A Namespaces group related config values and allow dot notation access, improving organization and type safety.

B Namespaces automatically validate config values against a schema without extra setup.

C Namespaces flatten all config keys into a single level object for easier access.

D Namespaces prevent any runtime changes to configuration values once loaded.

💡 Hint

Think about the purpose of namespaces and how they affect config access.

Namespaces in NestJS group related configuration values and support dot notation for easy access. They do not automatically validate or flatten keys, nor do they prevent runtime changes by default.