Question Set 3 ( .NET 8 )

Welcome to the quiz! Please read the following rules carefully before you begin:

Total Questions: The quiz consists of 10 questions.

No Time Limit: There is no time limit for completing the quiz. Take your time to think through each question.

Changing Answers: You are allowed to change your answers at any time before submitting the quiz.

Results: You will be able to see your results immediately after completing the quiz. This will include your score and the correct answers.

Your .NET Framework 4.5 application includes platform-specific code that relies on Windows-only features. How should you handle this code during the migration to .NET Core 6.0?

Handling Platform-Specific Code

Continue using Windows-only features and accept that the application will not be cross-platform.

Use platform-specific libraries and wrap them in a .NET Core-compatible API layer.

Remove the platform-specific code entirely and modify the application’s functionality.

Refactor or replace platform-specific code with cross-platform alternatives or use conditional compilation to handle platform-specific logic.

None

In your .NET Framework 4.5 application, you use web.config to handle different configurations for development and production environments. How should you manage environment-specific configurations in .NET Core 6.0?

Configuration for Development and Production Environments

Use a single appsettings.json file and manually check the environment within the application code.

Use multiple appsettings.json files, such as appsettings.Development.json and appsettings.Production.json, and configure environment-specific settings accordingly.

Configure environment-specific settings in a separate database and retrieve them at runtime.

Continue using web.config and manually manage different configurations for each environment.

None

Your .NET Framework 4.5 application uses NuGet packages. How should you handle package management in .NET Core 6.0?

NuGet Package Management

Continue using NuGet packages as they are compatible with .NET Core 6.0.

Manually download and reference NuGet packages without using the NuGet package manager.

Use a different package management system that is compatible with .NET Core 6.0.

Remove all NuGet packages and use only built-in libraries.

None

Your application uses Razor views for rendering HTML in .NET Framework 4.5. What is the approach for handling Razor views in .NET Core 6.0?

Razor Views

Use a third-party view engine that is compatible with .NET Core 6.0.

Continue using Razor views as they are fully supported in .NET Core 6.0.

Switch to using server-side Blazor for rendering views.

Replace Razor views with traditional ASPX pages.

None

Your .NET Framework 4.5 application uses System.Threading.Tasks for background tasks. How should you handle background services in .NET Core 6.0?

Background Services

Implement background tasks using a third-party task scheduler library.

Continue using System.Threading.Tasks for background processing.

Use Windows Services to manage background tasks.

Use the BackgroundService class in ASP.NET Core for background tasks.

None

Your .NET Framework 4.5 application uses a custom CORS policy. How should you configure CORS in .NET Core 6.0?

Cross-Origin Resource Sharing (CORS)

Use the AddCors method in Startup.cs or Program.cs to configure CORS policies.

Handle CORS in a custom middleware without using built-in features.

Avoid configuring CORS and rely on default policies.

Configure CORS policies in web.config file.

None

Your .NET Framework 4.5 application uses try-catch-finally blocks for exception handling. What is the best approach for exception handling in .NET Core 6.0?

Exception Handling

Use the built-in exception handling middleware to handle exceptions globally.

Use only catch blocks without finally for exception handling.

Implement a custom global exception handler manually in each controller.

Continue using try-catch-finally blocks as they are supported in .NET Core 6.0.

None

Your .NET Framework 4.5 application uses In-Proc session state. How should you handle session state in .NET Core 6.0?

Session State

Use distributed session state providers such as Redis or SQL Server for session state management.

Avoid using session state and refactor the application to use alternative state management.

Implement custom session state management from scratch.

Continue using In-Proc session state as it is supported in .NET Core 6.0.

None

Your .NET Framework 4.5 application serves static files from a specific directory. How should you configure static file serving in .NET Core 6.0?

Static Files Handling

Use a third-party library to handle static file serving.

Serve static files directly from a custom middleware.

Configure static file serving in Startup.cs using app.UseStaticFiles().

Continue using the previous static file serving configurations from .NET Framework.

None

10.

When migrating your application to .NET Core 6.0, what should you be aware of regarding SDK and runtime versions?

.NET Core SDK Versions

Use the latest available .NET Core SDK and runtime versions regardless of compatibility with your project.

Manually manage SDK and runtime versions through configuration files.

Use .NET Framework SDK alongside .NET Core SDK for migration purposes.

Ensure that the .NET Core SDK and runtime versions match the target framework specified in your project file.

None

11.

Your .NET Framework 4.5 application uses ASP.NET Web API. How should you migrate this to .NET Core 6.0?

Web API

Switch to WCF services as an alternative.

Rebuild the API using raw HTTP handling without a framework.

Migrate to ASP.NET Core Web API, which is integrated into the ASP.NET Core framework.

Continue using ASP.NET Web API, as it is fully supported in .NET Core 6.0.

None

12.

Your application uses ASP.NET Membership and Roles for authentication and authorization. How should you address this in .NET Core 6.0?

Authentication and Authorization

Continue using ASP.NET Membership and Roles as they are supported in .NET Core 6.0.

Use Windows Authentication only, as ASP.NET Membership is not supported.

Switch to ASP.NET Core Identity, which provides more modern and flexible authentication and authorization.

Implement a custom authentication and authorization system.

None

13.

In your .NET Framework 4.5 application, you use Global.asax for application startup logic. How should you handle application startup in .NET Core 6.0?

Application Startup

Continue using Global.asax for application startup.

Use the Startup.cs class to configure services and the app’s request pipeline.

Use an external configuration file for application startup settings.

Implement startup logic directly in the Program.cs file.

None

14.

Your application relies on HttpModules and HttpHandlers in .NET Framework 4.5. How should you handle request processing in .NET Core 6.0?

Middleware Usage

Implement custom request processing logic directly in your controllers.

Revert to using HttpModules in a .NET Framework application.

Continue using HttpModules and HttpHandlers as they are supported in .NET Core 6.0.

Replace them with middleware components in the ASP.NET Core pipeline.

None

15.

Your .NET Framework 4.5 application uses log4net for logging. What is the best approach for logging in .NET Core 6.0?

Logging Approach

Use a different third-party logging framework that is not compatible with .NET Core.

Switch to the built-in logging framework in .NET Core for better integration.

Continue using log4net as it is supported in .NET Core 6.0.

Manually implement a custom logging solution similar to log4net.

None

16.

Your .NET Framework 4.5 application does not use dependency injection. How should you address this in .NET Core 6.0?

Dependency Injection

Manually implement dependency injection as there is no built-in support in .NET Core.

Leverage the built-in dependency injection framework provided by .NET Core.

Use a third-party dependency injection library that is not designed for .NET Core.

Avoid using dependency injection to simplify the migration process.

None

17.

Your application uses Entity Framework 6 for data access. What should you do when migrating to .NET Core 6.0?

Entity Framework Migration

Continue using Entity Framework 6 as it is compatible with .NET Core 6.0.

Use both Entity Framework 6 and Entity Framework Core in the same application.

Migrate to Entity Framework Core for better compatibility and features with .NET Core.

Replace Entity Framework with direct ADO.NET calls.

None

18.

Your .NET Framework 4.5 application is built using Windows Forms. What should you consider when migrating to .NET Core 6.0?

UI Technology

Use a cross-platform UI framework like Blazor to rewrite the UI.

Continue using Windows Forms, as it is fully supported in .NET Core 6.0.

Migrate to a different platform that fully supports Windows Forms.

Redesign the application using WPF, as it is supported in .NET Core 6.0.

None

19.

In your .NET Framework 4.5 application, configuration settings are managed through a web.config file. How should you handle configuration in .NET Core 6.0?

Configuration Management

Continue using web.config as it is supported in .NET Core 6.0.

Switch to a config.xml file for configuration.

Use appsettings.json for configuration management.

Use app.config for configuration management.

None

20.

Your .NET Framework 4.5 application uses several libraries that are not supported in .NET Core 6.0. What is the recommended approach to handle these libraries during migration?

Library Compatibility

Wrap the libraries in a .NET Core-compatible service layer.

Continue using the .NET Framework version and avoid migration.

Rebuild the libraries from source to make them compatible with .NET Core.

Find .NET Core-compatible versions of the libraries and replace them.

None

1 out of 4

Time's up

Question Set 3 ( .NET 8 )

Leave a Reply Cancel reply