which apprach is better to to introduce an ID field or combine other fields?

[Qalife Qali]

I have the following problems when i am designing my database for an online exam system:-
1. I have a question table and answer table; where each question contains many answers and each answer have one question.
Now i have two approaches for designing the answer table, either by having:-

Answer_Id (PK),
Answer_Description,
Is_right.
Question_ID (FK)

Or

Answer_description
Is_right.
Question_ID (FK)
Having PK (Question_ID & Answer_description).

2. Same issue applies for this scenario; I have an article table and a comment table, where each article can have many comments and each comment can belong to an article.

Now i have two approaches for designing comment table, either by having:-
Comment_ID (PK)
article_ID (FK)
Comment_Desc
Created_BY
Created_time

Or

article_ID (FK)
Comment_Desc
Created_BY
Created_time

Having PK(Created_BY & Created_Date), since it s not possible to be able provide two comment at the same time!by the same user!!

So is it better to introduce the ID field for both (comment & answers) tables or having my PK by combining the available columns
Thanks in advance for any help.

 

[Ratchetr]

I would consider a 3'rd alternative for the first one: Don't put Is_right in the answer table. Put the Answer_Id of the right answer in the question table.
Why would I do it that way? You can reuse answers. Suppose you use All of the Above and None of the Above. a lot. Well, you really only need 1 row for each answer, but sometimes it will be right, and sometimes it will be wrong.

For the second, I would go with your first one. Comment should have a single, unique primary key. It will simplify what you need to store to be able to reference a comment later (say to reply to it, or edit it, or delete it. If you just have to store a single number, it's easier for the code using the database).