DSC – configure pull client LCM for multiple config names

I’m trying to understand how to configure the LCM on pull clients in general, but what I really need to understand is what I set in the LCM configuration script for each client in the config names section. Specifically, in the case when I may want multiple config names for each node. I’ve been using config names that matched the server name, but I’m trying to standardize to where I have say 3 different configs that are deploy ed to a fleet of servers in various combinations. Can someone give me a very basic example of two configuration scripts and a LCM configuration script that sets up a node to pull those two configurations?

Isn’t this an example of how removing the config ID requirements prior verisons offers more flexibility? What I mean is in the past you could only have one config ID for a node so you could only have one configuration to push right? And now you should be able to set the config name as an array of config names and have multiple distinct configurations deployed on one node, right? This last bit is what I am hoping to see a example of.