Monitors unauthorized or suspicious user activity, prevents you from creating misconfigurations on your resources in OCI, and helps detect misconfigured resources, such as publicly accessible Object Storage buckets, instances, and restricted ports on security lists. The explanation is that Cloud Guard is a service that helps you improve the security posture of your tenancy by providing visibility into your cloud resources, identifying security misconfigurations and threats, and taking corrective actions to remediate them. Cloud Guard monitors user activity and resource configurations using data collectors and detectors, evaluates them against predefined or custom rules, generates problems and recommendations based on severity levels, and executes responders to fix the issues automatically or manually.

From the version 1 menu on the OCI console, select ''Promote to Current''. The explanation is that when you promote a secret version to current, it becomes the latest version of the secret and is used by default when you access the secret. This way, you can rollback to a previous version of the secret without creating a new version.

The explanation is that the OCI Network Load Balancer supports three protocols: UDP, TCP, and ICMP. These protocols are used to distribute traffic across multiple backend servers based on different criteria, such as source and destination IP addresses, ports, and ICMP types and codes.

Customer Premises Equipment (CPE). The explanation is that CPE is an object in OCI that represents your on-premises router or VPN device that connects to your VCN via a site-to-site VPN. A site-to-site VPN is a secure and encrypted connection between your on-premises network and your VCN over the public internet. To set up a site-to-site VPN, you need to create a CPE object with your router's public IP address and other information, such as vendor and platform. You also need to create a Dynamic Routing Gateway (DRG) object in your VCN and attach it to your VCN. Then, you need to create an IPSec connection between your CPE and DRG, which will create two redundant VPN tunnels for high availability.

By default, the primary VNIC of an instance in a subnet has one primary private IP address. A private IP can have an optional public IP assigned to it if it resides in a public subnet. The explanation is that a private IP address is an IPv4 address that is assigned to a VNIC and belongs to the CIDR block of the VCN or subnet. By default, the primary VNIC of an instance in a subnet has one primary private IP address, which is automatically assigned by OCI and cannot be changed. However, you can also assign secondary private IP addresses to a VNIC, either manually or automatically, up to a maximum of 31 per VNIC. A private IP address can have an optional public IP address assigned to it, which allows the instance to communicate with the internet. A public IP address can be either ephemeral or reserved, depending on whether you want to keep it after stopping or terminating the instance. A private IP address can only have a public IP address assigned to it if it resides in a public subnet, which means that the subnet's route table has a route rule that directs traffic to the internet gateway.