Oracle Updated 1z0-1072-22 Exam Questions and Answers by henryk

VCN A  (10.0.0.0/16)  will use a range of IPS from 10.0.0.0 to 10.0.255.255 and VCN B (10.1.0.0/16) will use a range of IPS from 10.1.0.0 to 10.1.255.255 so will not be any Overlap between 2 VCNs

You can scale up/down your Autonomous Database to scale both in terms of compute (CPU) and storage only when needed, allows people to pay per use.

Oracle allows you to scale compute and storage independently, no need to do it together. these scaling activities fully online (no downtime required)

in Details page Autonomous Database in OCI console, click Scale Up/Down. Click on arrow to select a value for CPU Core Count or Storage (TB).

Or Select auto scaling to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand, compared to the database operating with auto scaling disabled.

Remote VCN peering is the process of connecting two VCNs in different regions (but the same tenancy ). The peering allows the VCNs' resources to communicate using private IP addresses without routing the traffic over the internet or through your on-premises network. Without peering, a given VCN would need an internet gateway and public IP addresses for the instances that need to communicate with another VCN in a different region.

At a high level, the Networking service components required for a remote peering include:

- Two VCNs with non-overlapping CIDRs, in different regions that support remote peering. The VCNs must be in the same tenancy.

- A dynamic routing gateway (DRG) attached to each VCN in the peering relationship. Your VCN already has a DRG if you're using an IPSec VPN or an Oracle Cloud Infrastructure FastConnect private virtual circuit.

A remote peering connection (RPC) on each DRG in the peering relationship.

A connection between those two RPCs.

Supporting route rules to enable traffic to flow over the connection, and only to and from select subnets in the respective VCNs (if desired).

Supporting security rules to control the types of traffic allowed to and from the instances in the subnets that need to communicate with the other VCN.

You can permanently terminate (delete) instances that you no longer need. Any attached VNICs and volumes are automatically detached when the instance terminates. Eventually, the instance's public and private IP addresses are released and become available for other instances. By default, the instance's boot volume is deleted when you terminate the instance, however you can preserve the boot volume associated with the instance, so that you can attach it to a different instance as a data volume, or use it to launch a new instance.

Dense I/O Shapes Designed for large databases, big data workloads, and applications that require high-performance local storage. DenseIO shapes include locally-attached NVMe-based SSDs.

so once you create the VM.DenseIO you need to moce the Database to locally-attached NVMe-based SSDs