EF Core - Why cascaded delete is forced in migration scripts for required navigations

Question

can anybody explain me following behaviour?

Following configuration for a navigation:

 modelBuilder.Entity()
                     .HasOne