On Junos switching platforms commonly used in data centers, a VLAN is a Layer 2 construct that defines a broadcast domain. To make a VLAN usable, you define the VLAN using a name and typically a VLAN ID, then associate Layer 2 interfaces with it so traffic entering those interfaces is placed into that VLAN. Without membership on interfaces, the VLAN exists in configuration but does not carry user traffic, because no ports participate in that broadcast domain.
Trunk mode interfaces are specifically designed to carry traffic for multiple VLANs over a single physical link, such as between switches, to servers using tagging, or to other network devices that understand VLAN tags. In Junos, trunking is implemented by allowing a list of VLAN IDs on the trunk so the interface accepts and forwards frames for those VLANs. This makes statement C correct.
An IRB interface is not mandatory for every VLAN. IRB is used when you want Layer 3 routing for a VLAN, typically to provide a default gateway and enable inter VLAN routing. Pure Layer 2 VLANs do not require IRB, which makes statement A incorrect.
Access mode interfaces are intended to connect to a single endpoint and carry traffic for a single VLAN, so assigning multiple VLANs to an access interface is not correct in standard access mode behavior, making statement D incorrect.