The set of names will be different for each respondent. If you want the actual name corresponding to a respondent's choice you need to cross reference the corresponding embedded data field value (e.g., Choice 1 = ChildName1 = John).

Thank you for replying. That's correct. The set of names are different, as are all the other embedded data fields. They authenticate first by email address and then their associated information pipes into the embedded data fields in the results.
For this particular question, we use embedded data fields as answer options - choice 1 is child 1, choice 2 is child 2, etc. and correct child name populates as expected.
It's when I export the results that I am having trouble. I see all their other embedded data as expected - however, the answers they select to this question don't populate as the child's name they selected, but instead as the code for the piped text.
Does that help or am I missing what you're saying?

Yes, you are missing my point. The behavior you are seeing is expected. In order to get the name you need to cross reference (i.e., lookup) the appropriate embedded data field. For example, if the person selected the second choice (i.e, ${e://Field/ChildName2}), to get the actual name you need to look at the value of ChildName2.

Hmmm...ok. Thank you for clarifying. Doesn't seem too efficient to have to pull in 3 additional fields to results vs having the selected answers pipe in to the results for this question. Regardless, I appreciate your time! Thank you!