This is explained in the docs, in Options pattern in ASP.NET Core. How you read the configuration settings depends on the interface you use. This is described in the section with the unintuitive title Options interfaces. I doubt anyone would think to go to that section if one didn't already know about eg IOptionsMonitor.

As that section explains:

• IOptions<> is indeed a singleton, loads the values at startup and doesn't show any changes.
• IOptionsMonitor will raise notifications every time there's a change and allow you to retrieve the latest value. This means that you can easily read two different values for the same setting in the same action.

Imagine trying to calculate a price while a fee or commission setting changes. This can be annoying.

• IOptionsSnapshot<> is scoped, will load the settings when the scope starts and won't changed during the scope, even if the underlying settings change. If your Options object has a Fee property, that will stay the same even if the actual setting changes.

You specify how you want to retrieve the values by using the appropriate interface in your controller, BackgroundService or other DI service class, eg :

class MyController:ControllerBase
{

    IOptionsSnapshot<Fees> _fees;

    public MyController(IOptionsSnapshot<Fees> feeOptions)
    {
        _fees=feeOptions'
    }
    ...
}

The section Use IOptionsSnapshot to read updated data offers more examples