Deciding fact and dimension tables

Imagine that you love running and data. It's only natural that you begin collecting data on your weekly running routine. You're most concerned with tracking how long you are running each week. You also record the route and the distances of your runs. You gather this data and put it into one table called Runs with the following schema:

runs
duration_mins - float
week - int
month - varchar(160)
year - int
park_name - varchar(160)
city_name - varchar(160)
distance_km - float
route_name - varchar(160)

After learning about dimensional modeling, you decide to restructure the schema for the database. Runs has been pre-loaded for you.

Question

Out of these possible answers, what would be the best way to organize the fact table and dimensional tables?

Possible Answers

A fact table holding duration_mins and foreign keys to dimension tables holding route details and week details, respectively.
A fact table holding week,month, year and foreign keys to dimension tables holding route details and duration details, respectively.
A fact table holding route_name,park_name, distance_km,city_name, and foreign keys to dimension tables holding week details and duration details, respectively.

Exercise

Deciding fact and dimension tables

Instructions 1/2

Question

Possible Answers