The correct option is Trigger When an issue is created Condition If an epic exists Action Edit issue fields "Due Date".

This rule uses the issue created trigger so it runs when a new issue is added. The condition ensures the rule only proceeds when a parent epic exists and the edit issue fields action can copy the epic's due date into the newly created issue by using automation smart values when setting the Due Date field.

Trigger When an issue is created Condition Issue type equals Epic Action Edit issue fields "Due Date" is incorrect because it only fires when the created issue is an epic. The requirement is to set the due date on a new issue that is linked to an existing epic and not to act only when the created issue itself is an epic.

Trigger When an issue is created and associated to an epic Action Edit issue fields "Due Date" is incorrect because there is no standard single trigger named associated to an epic and because the safe pattern is to trigger on creation and then verify a parent epic exists. Explicitly checking for the epic prevents the rule from running for unrelated issues.

Trigger When an issue is created Branch rule For parent epic Action Edit issue fields "Due Date" is incorrect because branching into the parent epic changes the rule context to the epic. That pattern would target the epic unless you explicitly reference the newly created issue with smart values, so it is not the simplest or most direct way to copy the epic's due date into the new issue.

Full AWS Practitioner Certification Question