So, let's take a short look at the URLSession framework itself.
Generally, an app will only need to use one session instance, or in the case of tabbed and document-based applications, one session per tab or document window.
All tasks in any given session share configuration settings, some of which may be overridden by the individual request settings.