If you already know SQL Server but do not know SQL Clustering then you have a lot of learning to do. SQL Clustering introduces new and interesting ways to trash your data if you get things wrong.

My advice is to start with a SQL Cluster in your development environment, and spent 2 or 3 weeks trying to break it and then fixing the problems. You should then have the skills you need to troubleshoot problems you might get in Production.

This assumes that Clustering is the right answer for your problem. SQL Clustering gives high availability but not high resilience. There are many single points of failure in SQL Clustering, so if you want high resilience then you need a different solution. Have you considered database mirroring or Peer to Peer replication - both of these options give you high resilience as wel as high availability.