For your problem, if I take it that the 3x Vector2 nodes are your coordinates of A, B and C (going from the top being A, middle being B and bottom being C), there are 2 possible solutions.
First, you can just directly link the 3 coordinates output nodes to the Set Local Position node just as you have illustrated in yellow. The trick is not on that part, but prior to that part anyway.
Option A)
You can simply re-link the Switch to their actual proper coordinate.
So, it would be like the output nodes on the Switch statement goes as this:
1→(0,-1720)
2→(0,-2900)
3→(0,-540)
Default→(0,-540)
In actuality, you could just remove the 3→ on the Switch node as it’s just a duplicate result of Default anyway OR just in case, I would recommend putting a 2nd link to the Default→ output of the Switch node toward a Debug Log message to print the value so you know that something is calling for a different value than 1 to 3.
Another thing to consider is that you’re starting your switch’s node cases at 1 instead of 0. While it’s common to start counting at 1 in our everyday life, computers always starts at 0 hence it’s always a good practice to consider 0 as 1, 1 as 2, 2 as 3 and so on when counting toward coding. (For example, if you build an Array or a List of stuff, the first in the list is at ID 0 and not ID 1)
Option B)
You may apply the conversion prior to the Switch node.
The blue link line between the Get Variable nod and the Switch node could be replaced with an “Add” node with its 2nd incoming link to an Integer variable of 1 (this would make it so that the Integer value given by your “Get Variable” node which target something written in Japanese (in your case) that I can’t read to be +1 in value. (So, 1 becomes 2, 2 becomes 3, etc.) Then you output that “Add” node" to a “Branch” node where you set the condition as if the value is higher than 3 (or whatever max value you need), the value becomes 1 (or whatever lowest value you set).
While Option A) is much simpler and easier to set up, it will requires you to redo every links in the coordinates whenever you add a new one. Option B) takes a bit more time (and visually seem a bit more clunky), but it best follow your logic and doesn’t requires as much changes if you add more coordinates to the lot. (Just got to change the max value set in the Branch’s IF condition.)