Downgrade Protection & CSOL

What are CSOL's three use cases?

When wiring the CSOL RFC from a managed dev system to SolMan, why must you NOT use a trusted RFC, and what do you use instead?

Name the five downgrade check types and the one whose warning you must NEVER ignore.

A developer asks you to relax the per-check-type severities in Downgrade Protection config because the errors are slowing them down. Why refuse, and where IS the legitimate place to make an exception?

CSOL warning mode and error mode both surface a conflict with the same details. What's the one behavioral difference that actually decides which to deploy?

When does CSOL default mode stop being enough, forcing you to switch to expert mode for conflict analysis?

Downgrade protection guards both workbench and Customizing objects, but which object type is it most critical for, and why?

To enable downgrade protection you deploy the CTS_PLUG software component to SolMan and all managed systems. What's the one distribution mistake to avoid, and how do you check status?

Two transports touch the same object but CSOL raises NO conflict. What relationship between them explains that, and why is it safe?

In warning mode, a second developer hits a Transport-Generic Check popup because their object is already locked by CSOL. What's the right next step, and what does Ignore-and-Continue actually cost?

A landscape has Java and dual-stack systems and uses external transport tooling instead of ChaRM/QGM. Why might downgrade protection simply not apply, and where would conflicts appear if it did?

You want to be sure no downgrade conflict is lurking before a release wave. Why isn't the automatic check enough, and what do you run instead?

A developer is surprised CSOL let them save an object that another open transport already changed. When does CSOL actually raise a conflict, and how long does the lock live?

SolMan is down but developers must keep working with CSOL protection. What's the fallback, and what extra step is mandatory once SolMan returns?