1z0-1072-22 Oracle Cloud Infrastructure 2022 Architect Associate Questions and Answers

You create an internet gateway in the context of a specific VCN. In other words, the internet gateway is automatically attached to a VCN. However, you can disable and re-enable the internet gateway at any time.

For traffic to flow between a subnet and an internet gateway, you must create a route rule accordingly in the subnet's route table (for example, destination CIDR = 0.0.0.0/0 and target = internet gateway). If the internet gateway is disabled, that means no traffic will flow to or from the internet even if there's a route rule that enables that traffic.

For the purposes of access control, you must specify the compartment where you want the internet gateway to reside. If you're not sure which compartment to use, put the internet gateway in the same compartment as the cloud network.

References: https://cloud.oracle.com/governance/identity/faq

https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/dbaascli.html

Using the dbaascli utility, you can:

Change the password of a database user.

Start and stop a database.

Start and stop the Oracle Net listener

Check the status of the Oracle Data Guard configuration.

Perform switchover and failover in an Oracle Data Guard configuration.

Patch the database deployment.

Perform database recovery.

Rotate the master encryption key.

https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/dbaascli.html

References: https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/migrating.htm

Some of the characteristics and factors to consider when choosing a migration method are:

On-premises database versionDatabase service database versionOn-premises host operating system and versionOn-premises database character setQuantity of data, including indexesData types used in the on-premises databaseStorage for data stagingAcceptable length of system outageNetwork bandwidth

References: https://cloud.o racle.com/database/faq#backup

Can I set up Data Guard across Availability Domains?Yes, you can set up Data Guard in the same or different Availability Domains in a region. However, Oracle recommends that you set up your Data Guard configuration across Availability Domains.Can I set up Data Guard across Oracle Cloud Infrastructure regions?Yes, you can set up Data Guard across regions,

“but the Database Cloud Service Data Guard feature currently does not support it. ”

You can manually set up Data Guard across regions by logging on to your host and using DGMGRL. You must enable an internet gateway on the primary and standby DB system VCN for Data Guard to transport logs across regions. Learn more about DGMGRL.

To configure a Data Guard system across regions or between on-premises and Oracle Cloud Infrastructure DB systems, you must access the database host directly and use the DGMGRL utility.

https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/usingdataguard.htm

https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/managingVNICs.htm#Source/D

By default, every VNIC performs the source/destination check on its network traffic. The VNIC looks at the source and destination listed in the header of each network packet. If the VNIC is not the source or destination, then the packet is dropped.

If the VNIC needs to forward traffic (for example, if it needs to perform Network Address Translation (NAT)), you must disable the source/destination check on the VNIC. For instructions, see To update an existing VNIC. For information about the general scenario, see Using a Private IP as a Route Target.

On autonomous there’s no patching needed. But on the regular DB Cloud services you need to patch the DB and the OS. During the creation on the OCDB the first DB is created automatically

Oracle automatically takes care of Operating system Installation/Configuration,  Grid Infrastructure, ASM diskgroup Creation/Configuration , and database software Installation and first database on the DB System. that's all when Creating DB Systems. and then the customer responsible to apply the patches to the database and OS

References: https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm#services

References: https://cloud.oracle.com/networking/vcn/faq

References: https://www.terraform.io/docs/extend/writing-custom-providers.html

The database name must be unique among all Autonomous Data Warehouses and Autonomous Databases in your tenancy in the same region.

Terminating an Autonomous Transaction Processing database permanently deletes the instance and removes all automatic backups. You cannot recover a terminated database.

the maximum number of CPUs and maximum storage capacity that can be provisioned in Oracle Autonomous Database In the current release up to 128 CPUs and 128TB can be provisioned from the cloud console. Customers requiring more resources need to call their Oracle account team

References: https://www.oracle.com/cloud/storage/object-storage-faq.html

- Oracle Object Storage supports server-side encryption. All data stored in Oracle Object Storage is automatically encrypted

- Encryption is automatically enabled for all data with no action required on the part of customers.

- Oracle encrypt both the object data and the user-defined metadata associated with the object.

References: https://docs.cloud.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnectoverv iew.htm

You use a DRG when connecting your existing on-premises network to your virtual cloud network (VCN) with one (or both) of these:

IPSec VPN

Oracle Cloud Infrastructure FastConnect

You also use a DRG when peering a VCN with a VCN in a different region:

Remote VCN Peering (Across Regions)

You can permanently terminate (delete) instances that you no longer need.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.

You can use a boot volume backup to create an instance or you can attach it to another instance as a data volume. However before you can use a boot volume backup, you need to restore it to a boot volume.

A load balancer improves resource utilization, facilitates scaling, and helps ensure high

availability. You can configure multiple load balancing policies and application-specific health

checks to ensure that the load balancer directs traffic only to healthy instances. The load

balancer can reduce your maintenance window by draining traffic from an unhealthy

application server before you remove it from service for maintenance.

The Load Balancing service considers a server marked drain available for existing persisted

sessions. New requests that are not part of an existing persisted session are not sent to that

server.

Edit Drain State: Opens a dialog box in which you can change the drain state.

If you set the server's drain status to true, the load balancer stops forwarding

new TCP connections and new non-sticky HTTP requests to this backend server.

This setting allows an administrator to take the server out of rotation for

maintenance purposes.

e. Edit Offline State: Opens a dialog box in which you can change the offline

status.

If you set the server's offline status to true, the load balance forwards no ingress

traffic to this backend server.

In ATP Service Console,

In the activity screen allows you to perform some basic monitor database activity and SQL queries

In the administration screen allows you to perform some basic administration of the service, like reset the admin password and  set resource management rules

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 could have multiple private virtual circuits, for example, to isolate traffic from different parts of your organization (one virtual circuit for 10.0.1.0/24; another for 172.16.0.0/16), or to provide redundancy.

A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. In addition, the physical hardware in a fault domain has independent and redundant power supplies, which prevents a failure in the power supply hardware within one fault domain from affecting other fault domains.

To control the placement of your compute instances, bare metal DB system instances, or virtual machine DB system instances, you can optionally specify the fault domain for a new instance or instance pool at launch time. If you don't specify the fault domain, the system selects one for you. Oracle Cloud Infrastructure makes a best-effort anti-affinity placement across different fault domains, while optimizing for available capacity in the availability domain. To change the fault domain for an instance, terminate it and launch a new instance in the preferred fault domain.

Use fault domains to do the following things:

Protect against unexpected hardware failures or power supply failures.

Protect against planned outages because of Compute hardware maintenance.

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.

VCN1 (10.0.0.0/16) will use the IP Range from 10.0.0.0 to 10.0.255.255 and the VNC 2 (172.16.0.0/16) will use the IP Range from 172.16.0.0 to 172.16.255.255 the will not be overlap between the 2 VCN

The Oracle Cloud Infrastructure provider is used to interact with the many resources supported by the Oracle Cloud Infrastructure. The provider needs to be configured with credentials for the Oracle Cloud Infrastructure account.