You might already be able to see that Automated Linked Clone Floating Pools have strong benefits and are a typical configuration. While it’s a strong architecture, it may not always be the best for every user group. Your solution may likely include both full clones and linked clones. Understanding the user groups that may be departmental and what applications they use will inform your direction for this. In most cases all users require a standard application stack such as Windows 10, O365, Adobe Reader, Flash, etc. However, in addition to this, you might have a department where a couple of users also require an additional 3rd party application. In this case, rather than creating a separate pool just for this small requirement, ThinApp could be utilized to capture the application and make it available to those two users in the desktop pool. This saves having to clone the master image, install the two applications and manage two master images.
It would not be good practice to create this desktop pool as full clones just because of those few requirements. Doing that might have a big effect on the underlying storage requirements and costs.
If you do have a scenario where an application cannot be ThinApp’d and a group of users must be able to for example install their own applications, that's a good indicator that an automated full clone pool is needed. Just be aware that your desktops in this pool may have a higher cost due to the increased storage (e.g. 25GB to 75GB) and also increased management (e.g. solution required to update/manage desktop – Altiris, SCCM).