Explanation/Reference:
In order to use the link aggregation function, it is necessary to configure beforehand the respective network devices as to which interfaces are aggregated as one group.
In more detail: Groups represent sets of actions for flooding as well as more complex forwarding semantics (e.g. multipath, fast reroute, and link aggregation). As a general layer of indirection, groups also enable multiple flow entries to forward to a single identifier (e.g. IP forwarding to a common next hop). This abstraction allows common output actions across flow entries to be changed efficiently.
Note: There are 4 types of groups:
All

All the action buckets in the group should be executed when a packet hits the group table.
Select

Execute any one action bucket in the group. The switch implementation uses round-robin to select the action bucket to be executed.
Indirect

Execute the one defined bucket in this group. This group supports only a single bucket.
Fast failover

Execute the first live bucket. The buckets are evaluated for liveness in the order defined by the group.
Note 2: Openflow specification defines a weight mechanism to do load sharing. However, this is not supported in the switch implementation. The weight MUST be given as 1. For all the other groups, weight MUST be specified as 0.
Incorrect Answers:
A: In Aggregation mode, all VLANs in the switch are part of an OpenFlow instance. The exception is the management VLAN and a VLAN that communicates to the controller. When Aggregation is configured, there is only OpenFlow traffic, no production traffic.
References: HP OpenFlow 1.3 Administrator Guide Wired Switches K/KA/KB/WB 15.15, page 32
http://h20565.www2.hpe.com/hpsc/doc/public/display?
sp4ts.oid=7074783&docLocale=en_US&docId=emr_na-c04217797