A Business Analyst (BA) noticed that one of the User Story Card files for the...

In the standard Guidewire User Story Card template (an Excel-based tool used for requirements gathering), version control is manually tracked to ensure auditability and clarity among the project team.

Document Control Tab (Option C):This is typically the first tab in the Story Card workbook. It contains a section specifically forAmendment History(or Revision History).

Content:This section is designed to capture:

Who:The author of the change.

When:The date of the change.

What/Why: A description of the modification (e.g., "Updated Acceptance Criteria based on Workshop feedback").

This provides the specific "Who, What, and Why" requested in the scenario.

Why other options are incorrect:

File > Properties (A):This is standard Excel metadata. It shows the "Last Modified By" user and date, but it cannot explainwhatspecific cells were changed orwhy(the business context).

Action Items (B):This tab tracks open questions or tasks, not the revision history of the document requirements.

UI Fields (D):This tab tracks the requirements for screen fields, but does not serve as a changelog for the entire document.