Standalone vs module-based decision in Angular - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When to prefer standalone components in Angular?

Which scenario best justifies using standalone components instead of module-based components in Angular?

A When you want to group many components and services together for lazy loading.

B When building a small feature that does not need to be reused across multiple modules.

C When you need to share components across multiple modules with complex dependencies.

D When you want to organize your app into feature modules for better scalability.

💡 Hint

Think about simplicity and avoiding extra setup for small, isolated components.

Standalone components are ideal for small, self-contained features that don't require the overhead of modules. They simplify the code and reduce boilerplate.

❓ component_behavior

intermediate

Effect of standalone flag on component imports

Given two Angular components, one standalone and one module-based, how does the standalone: true flag affect importing other components or directives?

A Standalone components import dependencies directly in their <code>imports</code> array, while module-based components rely on NgModules to provide dependencies.

B Standalone components cannot import other components or directives, only modules can.

C Module-based components import dependencies directly in their <code>imports</code> array, standalone components rely on NgModules.

D Both standalone and module-based components import dependencies the same way using NgModules.

💡 Hint

Consider where dependencies are declared for standalone components versus module-based components.

Standalone components declare their dependencies directly in their imports array, removing the need for NgModules to manage dependencies.

📝 Syntax

advanced

Correct syntax for declaring a standalone component

Which of the following Angular component declarations correctly defines a standalone component?

A @Component({ selector: 'app-test', template: '<p>Test</p>', standalone: true }) export class TestComponent {}

B @Component({ selector: 'app-test', template: '<p>Test</p>' }) export class TestComponent {}

C @Component({ selector: 'app-test', template: '<p>Test</p>', standalone: false }) export class TestComponent {}

D @Component({ selector: 'app-test', template: '<p>Test</p>', standalone: 'true' }) export class TestComponent {}

💡 Hint

Check the type and presence of the standalone property.

The standalone property must be a boolean true (not string) to declare a standalone component.

❓ lifecycle

advanced

Lifecycle differences between standalone and module-based components

Which statement about Angular component lifecycle hooks is true when comparing standalone and module-based components?

A Module-based components have additional lifecycle hooks not available in standalone components.

B Standalone components do not support lifecycle hooks like <code>ngOnInit</code>.

C Standalone components have the same lifecycle hooks and behavior as module-based components.

D Standalone components require manual invocation of lifecycle hooks.

💡 Hint

Think about whether Angular changes lifecycle behavior based on component type.

Standalone components behave the same as module-based components regarding lifecycle hooks; Angular treats them identically in this regard.

🔧 Debug

expert

Why does this standalone component fail to render?

Consider this standalone Angular component code snippet:

@Component({
  selector: 'app-sample',
  template: '
Hello
',
  standalone: true
})
export class SampleComponent {}

When used in an Angular app, it does not render and shows an error about missing imports. What is the most likely cause?

A The selector name must start with 'app-' to work correctly.

B Standalone components cannot be used without being declared in an NgModule.

C The <code>standalone</code> property must be set to false for the component to render.

D The component is missing the <code>imports</code> array to include CommonModule for common directives like <code>ngIf</code> or <code>ngFor</code>.

💡 Hint

Think about what Angular modules provide by default and what standalone components need to import explicitly.

Standalone components must explicitly import CommonModule to use common Angular directives. Without it, Angular throws errors about missing directives.

Practice

1. What is the main advantage of using standalone components in Angular?

easy

A. They automatically generate routing modules.

B. They enforce strict typing on all components.

C. They simplify small or new apps by removing the need for modules.

D. They require more boilerplate code than module-based components.

Solution

1. Step 1: Understand standalone components purpose

   Standalone components are designed to reduce complexity by not requiring Angular modules.

2. Step 2: Compare with module-based approach

   Module-based components need NgModules, which add overhead especially in small or new apps.

3. Final Answer:

   They simplify small or new apps by removing the need for modules. -> Option C

4. Quick Check:

   Standalone components = simpler setup [OK]

Hint: Standalone means no modules needed, good for small apps [OK]

Common Mistakes:

• Thinking standalone components generate routing automatically
• Believing standalone components add more code
• Confusing standalone with strict typing features

2. Which of the following is the correct syntax to declare a standalone component in Angular?

easy

A. @Component({ selector: 'app-example', standalone: true, template: 'Example' }) export class ExampleComponent {}

B. @NgModule({ declarations: [ExampleComponent], standalone: true }) export class ExampleModule {}

C. @Component({ selector: 'app-example', template: 'Example' }) export class ExampleComponent {}

D. @Component({ selector: 'app-example', standalone: false, template: 'Example' }) export class ExampleComponent {}

Solution

1. Step 1: Identify standalone component syntax

   Standalone components use @Component decorator with standalone: true property.

2. Step 2: Check options for correct usage

   @Component({ selector: 'app-example', standalone: true, template: '

   Example

   ' }) export class ExampleComponent {} correctly sets standalone: true inside @Component; others either misuse @NgModule or omit standalone.

3. Final Answer:

   @Component({ selector: 'app-example', standalone: true, template: '

   Example

   ' }) export class ExampleComponent {} -> Option A

4. Quick Check:

   Standalone flag inside @Component = correct syntax [OK]

Hint: Standalone must be true inside @Component decorator [OK]

Common Mistakes:

• Putting standalone inside @NgModule instead of @Component
• Omitting standalone property for standalone components
• Setting standalone to false for standalone components

3. Given this Angular setup, what will happen if you try to use ChildComponent inside ParentComponent without importing any module or standalone component?

medium

A. Angular will ignore ChildComponent and render ParentComponent only.

B. Angular will throw a compilation error because ChildComponent is not declared or imported.

C. ParentComponent will render but ChildComponent will be empty.

D. ChildComponent will render correctly because Angular auto-imports components.

Solution

1. Step 1: Understand Angular component usage rules

   Angular requires components to be declared in a module or imported as standalone to be used inside another component.

2. Step 2: Analyze the scenario without imports or declarations

   Without importing or declaring ChildComponent, Angular cannot recognize it and will throw a compilation error.

3. Final Answer:

   Angular will throw a compilation error because ChildComponent is not declared or imported. -> Option B

4. Quick Check:

   Missing import/declaration = compilation error [OK]

Hint: Always import or declare components before use [OK]

Common Mistakes:

• Assuming Angular auto-imports components
• Expecting empty rendering instead of error
• Thinking Angular silently ignores unknown components

4. You have a module-based Angular app but want to convert a component to standalone. Which error will you encounter if you forget to add imports for used Angular features like CommonModule?

medium

A. Template errors like 'ngIf' is not a known property or directive.

B. Runtime error: Cannot find module 'CommonModule'.

C. No errors, Angular auto-imports CommonModule.

D. Compilation error: Component must be declared in a module.

Solution

1. Step 1: Understand standalone component imports

   Standalone components must explicitly import Angular modules like CommonModule to use directives such as ngIf.

2. Step 2: Identify error from missing imports

   If CommonModule is missing, Angular template compiler reports errors that directives like ngIf are unknown.

3. Final Answer:

   Template errors like 'ngIf' is not a known property or directive. -> Option A

4. Quick Check:

   Missing CommonModule import = template directive errors [OK]

Hint: Standalone needs explicit imports for Angular directives [OK]

Common Mistakes:

• Assuming Angular auto-imports CommonModule
• Expecting runtime errors instead of template errors
• Confusing module declaration errors with import errors

5. You are building a large Angular app with many shared components. Which approach best supports easy sharing and organization?

hard

A. Avoid modules and import all components globally in main.ts.

B. Use only standalone components without any modules for all features.

C. Use standalone components but avoid importing any modules.

D. Use module-based components grouped in feature modules for better organization.

Solution

1. Step 1: Consider app size and sharing needs

   Large apps with many shared components benefit from modules to organize and share components efficiently.

2. Step 2: Evaluate approaches for large apps

   Module-based components grouped in feature modules provide clear boundaries and easier maintenance compared to standalone-only approaches.

3. Final Answer:

   Use module-based components grouped in feature modules for better organization. -> Option D

4. Quick Check:

   Large app + sharing = modules best [OK]

Hint: Big apps need modules for sharing and organization [OK]

Common Mistakes:

• Thinking standalone fits large apps better
• Importing all components globally causing clutter
• Ignoring module benefits for organization