RE: Clustered vs non clustered index
If we had put the files in the letter-ordered lockers from the very beginning, we would know that the files of the students starting with the letter A were in the 1st lockers in the 1st room. It would be much easier to find. (maybe 2th or 3th locker but we now room)
But if it is class-based, we will have to remove all the files from the lockers, sort them again and use them that way.
You have the right to create one cluster and it is useful to create it according to the query you use most frequently to get maximum efficiency.
But as I mentioned in the first example, there are extra situations that you should pay attention to.
If you're sorting by name and half the school is Tom, it means you haven't created a cluster index for half the records. In order to get efficiency from the cluster, it should be distributed more evenly.
Or, if the fields you select in the index change very often, the update process will be slow as it has to be physically relocated each time.