When you call a GET API call for users / groups / and other such objects, the response is usually Paginated, in case these are a lot of objects returned. What do you do in order to retrieve all objects?
Solution: You have to call a different API request for the next page, which will then provide another API call in the response headers of it - for the following page (in case there are still objects to be returned), till there are no more objects to be returned

In an SP-initiated SAML 2.0 flow, the SP will never redirect to Okta if the session is already active Solution: It will always redirect to Okta and in this case only - will promt the user for re-authentication by manually entering Okta credentials

When does Okta bring LDAP roles into Okta?
Solution: Only during an LDAP import

How can SAML provision attributes via JIT? Or even create users?
Solution: By including specific information in the assertion

In Okta's KB articles the set of functions under the 'Provisioning' concept are referred to as CRUD. This is a concept you also meet when referring to CRUD APIs. What about its meaning here, in Okta's vision?
Solution: In 'Provisioning', CRUD stands for Create, Read, Update, Deprovision