Sure, that's painfully easy to do in BDA. If you're using the GUI, you just specify which of the nodes you want to create the cluster on. When you select the group that will contain the clustered SQL Server instance, BDA will automatically make the node that the group is currently owned by part of the clustered SQL Server instance, and then it will present you with a widget allowing you to select what other nodes in the cluster you want to add to the clustered SQL Server instance:
(my cluster here only has two nodes, but you can imagine what it would look like with more nodes under the "Available" section)
In this screenshot, the cluster group I'd selected on the previous screen was active on node WI28-CL098-02, so that node was required to be in the clustered SQL Server instance (if you want a particular node to be the required node for your clustered SQL Server instance, make sure the cluster group you plan on creating the clustered SQL Server instance in is owned by that node before starting the Create Clustered SQL Server Instance wizard in BDA).
By default, BDA only creates the clustered SQL Server instance with the one required node. You have to select the additional nodes you want in the clustered SQL Server instance and move them into the "Selected" column for BDA to put more nodes into the clustered instance.
It's similarly easy to do so using the command line utilities: there is command-line utility that allows you to specify a BDA "Create Clustered SQL Server Instance" template for the job, and then only specify the version to be installed and the clustered SQL Server instance name on the command line. It's a bit much to try and fit into this response, but it's all in our command line utilities documentation.
Oh, and also BDA makes it painfully easy to add nodes to an existing clustered SQL Server instance later. It pretty much works the same way: you're presented with a list of available nodes, and you just move the ones over from the Available list to the Selected list and hit the "Run Job" button.