• arthurolcot (1/24/2013)


    Hugo Kornelis (1/24/2013)


    I think the correct answer should be worded slightly differently: "Either one can be appropriate" (italics used to emphasize changed part).

    If forced to make a choice based on the limited information given, my second choice would be a relational design with some XML columns for the less- and un-structured data.

    (My first choice would be to first read the documentation and conduct some interviews)

    +1

    I think there is a missing answer "Both together is appropriate" which I feel is probably the correct answer based on the poor question. In reality you would probably have a mostly relational database with some XML as required for some of the unstructured content. As such I went for relational and got it wrong as I wouldn't choose a pure XML repository to drive a website. You need a fair bit of data stored relationally. I don't mind getting questions wrong as it helps you to learn, but this is a pretty bad question...

    These were my exact thoughts - you may wish to use either but would probably end up using both in reality. This would be the tactic favoured by many CMS e.g. Umbraco, which might be used to drive such a site. I got it right though as none of the wrong answers were really feasible in my head at least even if the right one was not totally plausible.