Understanding ASP.NET Core and How It Differs from the Classic Framework Quiz

1. ASP.NET Core as a Cross-Platform Framework

   Which key feature enables ASP.NET Core applications to run on Windows, Linux, and macOS without modification?

   1. Cross-platform support
   2. Only-Windows compatibility
   3. Mono-integration
   4. Single-threaded execution
   5. Xamarin Forms

2. Open Source Nature of ASP.NET Core

   What distinguishes ASP.NET Core from its predecessor in terms of open source availability?

   1. ASP.NET Core is completely open source
   2. ASP.NET Core is only available as a paid product
   3. ASP.NET Core source code is hidden
   4. ASP.NET Core is closed source
   5. ASP.NET Core is in public alpha

3. Dependency Injection Built-in

   What built-in software design pattern does ASP.NET Core natively support for managing dependencies between classes?

   1. Dependency Injection
   2. Data Insertion
   3. Control Inversion
   4. Resource Isolation
   5. Direct Instantiation

4. Unified Programming Model

   Which approach does ASP.NET Core use to provide a unified model for building both web APIs and web applications?

   1. The unified programming model
   2. MVC Web Forms
   3. Page Controller Pattern
   4. Client-Side Integration
   5. Web API Exclusive

5. Performance Improvements

   Why is ASP.NET Core often considered faster than the classic ASP.NET Framework for web applications?

   1. It has a modular and lightweight architecture
   2. It uses global.asax for event handling
   3. It requires a web.config file for each application
   4. It relies on heavy server-side state management
   5. It only supports synchronous processing

6. Hosting Flexibility

   ASP.NET Core applications can be hosted in more ways than the classic Framework; which hosting option is new in ASP.NET Core?

   1. Self-hosting in a custom process
   2. IIS-only hosting
   3. Remote terminal services
   4. ActiveX hosting
   5. Windows Script Host

7. Configuration System

   Compared to earlier versions, what is a notable improvement of the configuration system in ASP.NET Core?

   1. Support for multiple configuration sources like JSON and environment variables
   2. Configuration only through XML files
   3. No configuration possible
   4. Requires registry editing
   5. Only uses INI files

8. Middleware Pipeline

   Instead of using the traditional HTTP modules and handlers, ASP.NET Core utilizes what concept for processing HTTP requests?

   1. Middleware pipeline
   2. Web forms lifecycle
   3. View state management
   4. Active components
   5. Direct mapping

9. Side-by-Side Versioning

   What versioning advantage does ASP.NET Core offer that the classic Framework lacks, allowing apps to run different versions on the same system?

   1. Side-by-side versioning
   2. Single-version constraint
   3. Direct code sharing
   4. Mandatory upgrades
   5. Inline version patching

10. Standardized Project Structure

    What is a characteristic of the default project structure in ASP.NET Core that simplifies development?

    1. A standardized and simplified directory layout
    2. A requirement to use legacy directories
    3. Multiple nested bin folders
    4. Exclusive use of App_Code folder
    5. Hard-coded library paths