Async configuration in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import ConfigModule asynchronously.

NestJS

import { ConfigModule } from '@nestjs/config';

@Module({
  imports: [ConfigModule.[1]({
    isGlobal: true,
  })],
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

Acreate

BforFeature

Cregister

DforRootAsync

Attempts:

3 left

💡 Hint

Common Mistakes

Using synchronous methods like forFeature instead of forRootAsync.

Trying to use register which is not a method of ConfigModule.

The forRootAsync method is used to configure modules asynchronously in NestJS.

2fill in blank

medium

Complete the code to provide a factory function for async config.

NestJS

ConfigModule.forRootAsync({
  useFactory: async () => {
    const config = await fetchConfig();
    return [1];
  },
}),

Drag options to blanks, or click blank then click option'

APromise.resolve(config)

Bconfig

Cawait config

D{ config }

Attempts:

3 left

💡 Hint

Common Mistakes

Returning an object with config as a property instead of the config itself.

Using await unnecessarily on a variable already awaited.

The factory function should return the config object directly.

3fill in blank

hard

Fix the error in the async config provider by completing the inject array.

NestJS

ConfigModule.forRootAsync({
  imports: [HttpModule],
  useFactory: async (httpService: HttpService) => {
    const response = await httpService.get('url').toPromise();
    return response.data;
  },
  inject: [[1]],
}),

Drag options to blanks, or click blank then click option'

AHttpModule

BHttpClient

CHttpService

DHttp

Attempts:

3 left

💡 Hint

Common Mistakes

Injecting the module instead of the service.

Using incorrect service names like HttpClient.

The inject array must list the provider tokens to inject, here HttpService.

4fill in blank

hard

Fill both blanks to create an async config that uses a class provider.

NestJS

ConfigModule.forRootAsync({
  useClass: [1],
  imports: [[2]],
}),

Drag options to blanks, or click blank then click option'

AConfigService

BHttpModule

CConfigModule

DAppModule

Attempts:

3 left

💡 Hint

Common Mistakes

Using the module name instead of the service class for useClass.

Importing the wrong module or no module at all.

The useClass option expects a class like ConfigService, and HttpModule is imported for HTTP features.

5fill in blank

hard

Fill all three blanks to create a complete async config with useFactory, inject, and imports.

NestJS

ConfigModule.forRootAsync({
  imports: [[1]],
  useFactory: async (configService: [2]) => {
    const settings = await configService.loadSettings();
    return settings;
  },
  inject: [[3]],
}),

Drag options to blanks, or click blank then click option'

AHttpModule

BConfigService

DAppModule

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up module and service names in imports and inject arrays.

Not importing the module that provides the injected service.

Import HttpModule for HTTP features, inject ConfigService to use in the factory function.

Practice

1. What is the main purpose of using forRootAsync in NestJS configuration?

easy

A. To disable configuration loading in the app

B. To synchronously load configuration from a static file

C. To load configuration asynchronously, allowing external calls before app starts

D. To automatically reload configuration on every request

Solution

1. Step 1: Understand async config purpose

   forRootAsync is designed to load configuration that requires asynchronous operations like fetching from a remote service.

2. Step 2: Compare options

   Options A, B, and D do not describe asynchronous loading or external calls. Only To load configuration asynchronously, allowing external calls before app starts correctly states the purpose.

3. Final Answer:

   To load configuration asynchronously, allowing external calls before app starts -> Option C

4. Quick Check:

   Async config = forRootAsync usage [OK]

Hint: Async config means waiting for external data before app starts [OK]

Common Mistakes:

• Thinking forRootAsync loads config synchronously
• Confusing forRootAsync with auto-reload features
• Assuming it disables config loading

2. Which of the following is the correct syntax to use forRootAsync with a factory function in NestJS?

easy

A. ConfigModule.forRoot({ useFactory: () => ({ key: 'value' }) })

B. ConfigModule.forRootAsync({ useFactory: () => 'value' })

C. ConfigModule.forRootAsync({ factory: () => ({ key: 'value' }) })

D. ConfigModule.forRootAsync({ useFactory: async () => ({ key: 'value' }) })

Solution

1. Step 1: Identify correct method and property names

   The method is forRootAsync and the correct property for async config is useFactory.

2. Step 2: Check syntax correctness

   ConfigModule.forRootAsync({ useFactory: async () => ({ key: 'value' }) }) uses forRootAsync with useFactory returning an object asynchronously, which is correct. ConfigModule.forRoot({ useFactory: () => ({ key: 'value' }) }) uses forRoot which is synchronous. ConfigModule.forRootAsync({ factory: () => ({ key: 'value' }) }) uses wrong property factory. ConfigModule.forRootAsync({ useFactory: () => 'value' }) returns a string instead of an object.

3. Final Answer:

   ConfigModule.forRootAsync({ useFactory: async () => ({ key: 'value' }) }) -> Option D

4. Quick Check:

   Correct syntax = ConfigModule.forRootAsync({ useFactory: async () => ({ key: 'value' }) }) [OK]

Hint: Use forRootAsync with useFactory returning config object [OK]

Common Mistakes:

• Using forRoot instead of forRootAsync
• Using wrong property name like 'factory'
• Returning non-object from factory

3. Given this NestJS async config snippet, what will be the resolved configuration object?

ConfigModule.forRootAsync({
  useFactory: async () => {
    const apiKey = await Promise.resolve('12345');
    return { apiKey };
  }
})

medium

A. { apiKey: '12345' }

B. { apiKey: Promise }

C. undefined

D. Throws runtime error

Solution

1. Step 1: Understand async factory behavior

   The factory function awaits a resolved promise returning '12345' and returns an object with apiKey property.

2. Step 2: Determine final config object

   The returned object is { apiKey: '12345' }, not a promise or undefined, and no error is thrown.

3. Final Answer:

   { apiKey: '12345' } -> Option A

4. Quick Check:

   Async factory returns resolved object [OK]

Hint: Async factory returns awaited object, not promise [OK]

Common Mistakes:

• Thinking config is a Promise object
• Assuming undefined because of async
• Expecting runtime errors from await

4. Identify the error in this async configuration setup:

ConfigModule.forRootAsync({
  useFactory: () => {
    const secret = fetchSecret();
    return { secret };
  }
})

async function fetchSecret() {
  return 'topsecret';
}

medium

A. useFactory must be async to await fetchSecret

B. fetchSecret should not be async

C. Return value must be a string, not object

D. No error, code is correct

Solution

1. Step 1: Analyze async function usage

   fetchSecret is async and returns a Promise. useFactory calls it but does not await, so secret is a Promise, not the resolved value.

2. Step 2: Fix the factory function

   useFactory must be declared async and await fetchSecret to get the actual secret string before returning the config object.

3. Final Answer:

   useFactory must be async to await fetchSecret -> Option A

4. Quick Check:

   Async calls need await in factory [OK]

Hint: Async calls inside factory require async/await [OK]

Common Mistakes:

• Forgetting to mark useFactory async
• Returning unresolved Promise as config value
• Assuming fetchSecret sync

5. You want to load configuration asynchronously from a database service in NestJS. Which setup correctly injects the service and uses it in forRootAsync?

hard

A. ConfigModule.forRootAsync({ useFactory: () => dbService.getConfig(), inject: [DatabaseService] })

B. ConfigModule.forRootAsync({ useFactory: async (dbService) => await dbService.getConfig(), inject: [DatabaseService] })

C. ConfigModule.forRootAsync({ useFactory: async () => await dbService.getConfig() })

D. ConfigModule.forRoot({ useFactory: async (dbService) => await dbService.getConfig(), inject: [DatabaseService] })

Solution

1. Step 1: Understand dependency injection in async config

   To use a service inside useFactory, it must be injected via the inject array and passed as a parameter.

2. Step 2: Check async usage and method call

   ConfigModule.forRootAsync({ useFactory: async (dbService) => await dbService.getConfig(), inject: [DatabaseService] }) correctly marks useFactory async, injects DatabaseService, and awaits getConfig(). Options B and C miss injection or async. ConfigModule.forRoot({ useFactory: async (dbService) => await dbService.getConfig(), inject: [DatabaseService] }) uses forRoot which is synchronous.

3. Final Answer:

   ConfigModule.forRootAsync({ useFactory: async (dbService) => await dbService.getConfig(), inject: [DatabaseService] }) -> Option B

4. Quick Check:

   Inject services and await async calls in forRootAsync [OK]

Hint: Inject services and await async calls in useFactory [OK]

Common Mistakes:

• Not injecting the service in inject array
• Using forRoot instead of forRootAsync
• Not marking useFactory async when awaiting