Which TWO statements are TRUE about Private IP addresses in Oracle Cloud Infrastructure (OCI)?

When an Oracle Cloud Infrastructure (OCI) compute instance is launched, its primary Virtual Network Interface Card (VNIC) is automatically created and assigned a single primary private IP address from the chosen subnet's CIDR block. This is the default and fundamental behavior. Furthermore, for a private IP to be accessible from the internet, it can be mapped to a public IP address. This assignment is optional and is only possible if the VNIC resides in a public subnet, which is a subnet configured with a route table that has a route to an internet gateway.

A. By default, only a primary private IP is assigned. Secondary private IPs must be explicitly added after the instance is created; they are not assigned by default.
B. A VNIC can have multiple private IP addresses. It always has one primary private IP and can be assigned multiple secondary private IPs, with the limit depending on the instance shape.

1. Oracle Cloud Infrastructure Documentation, "Overview of Private IP Addresses". This document states, "Every VNIC has a primary private IP address, and you can add secondary private IP addresses." This confirms that a VNIC can have more than one private IP (invalidating option B) and that secondary IPs are added, not assigned by default (invalidating option A).

2. Oracle Cloud Infrastructure Documentation, "Virtual Network Interface Cards (VNICs)", Section: "How VNICs Work". This section details, "When you launch an instance, a primary VNIC is created for the instance... The instance gets a primary private IP address from the CIDR block of that subnet." This directly supports the correctness of option C.

3. Oracle Cloud Infrastructure Documentation, "Public IP Addresses", Section: "Overview of Public IP Addresses". This source explains, "You can optionally assign a public IP address to an instance... The instance must be in a public subnet." This confirms that assigning a public IP to a private IP is an optional action contingent on being in a public subnet, supporting option D.