Best Practices For Using MVC With A Dictionary-like Model?

I'm about to begin an ASP.NET MVC project and I'm not sure how to approach an aspect of the design. Basically, there is a user site and an admin site. In the admin sites, administartors design a form and send an e-mail link out to a handful of people. When the users click on the link, they are sent to the form.

Essentially what I'm wondering is what are the best practices when the model resembles looks more like a dictionary than a table?

In other words, instead of:

CREATE TABLE FormResponse (ResponseId, FormId, UserId, FirstName, LastName, BirthDay, Comments)

...containing 1 row per complete response

It's more like:

CREATE TABLE FormResponse (ResponseId, FormId, UserId, QuestionId, Value)

...containing 4 rows. 1 for the FirstName, 1 for the LastName, 1 for the BirthDay, and 1 for Comments.