Does inserting new data into a sorted clustered columnstore index in SQL Server disrupt the order?

I'm working with clustered columnstore indexes in SQL Server and have a question about maintaining data order. I understand that by default, clustered columnstore indexes don't sort data. I've seen a technique where people: - Create a clustered rowstore index to sort the data - Then use the DROP_EXISTING option to create a clustered columnstore index This results in a clustered columnstore index with initially sorted data. However, I'm concerned about what happens when new data is inserted. My questions are: * Does inserting new data into this table disrupt the existing order? * If so, are there any ways to prevent this or maintain the order over time? I'd appreciate insights from anyone who has experience with this scenario or knowledge about the internal workings of columnstore indexes in SQL Server. Thanks in advance for your help!