Free 1Z0-1072-22 Exam Dumps Preview

The second tool, OCI IP Troubleshooting, helps troubleshoot issues with public facing IP addresses. This feature is also part of our Internet Intelligence toolset, providing analytical insight to help network operations teams reduce the time it takes to troubleshoot an issue by providing awareness of availability and latency across the Internet.
Ref:
https://blogs.oracle.com/cloud-infrastructure/internet-intelligence,-now-available-in-the-oracle-cloud-infrastructure-console

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

When you create a subnet, by default it's considered public, which means instances in that subnet are allowed to have public IP addresses. Whoever launches the instance chooses whether it will have a public

IP address. You can override that behavior when creating the subnet and request that it be private, which means instances launched in the subnet are prohibited from having public IP addresses. Network administrators can therefore ensure that instances in the subnet have no internet access, even if the VCN has a working internet gateway, and security rules and firewall rules allow the traffic.
There are two optional gateways (virtual routers) that you can add to your VCN depending on the type of
internet access you need:
Internet gateway: For resources with public IP addresses that need to be reached from the internet (example: a web server) or need to initiate connections to the internet. NAT gateway: For resources without public IP addresses that need to initiate connections to the internet (example: for software updates) but need to be protected from inbound connections from the internet.
Just having an internet gateway alone does not expose the instances in the VCN's subnets directly to the internet. The following requirements must also be met: The internet gateway must be enabled (by default, the internet gateway is enabled upon creation).
The subnet must be public.
The subnet must have a route rule that directs traffic to the internet gateway. The subnet must have security list rules that allow the traffic (and each instance's firewall must allow the traffic).
The instance must have a public IP address.

Session persistence is a method to direct all requests originating from a single logical client to a single backend web server. Backend servers that use caching to improve performance, or to enable log-in sessions or shopping carts, can benefit from session persistence

References:
https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/securitylists.htm?tocpath=Services%7CNetworking%7CAccess%20and%20Security%7C_____3

STRONG CONSISTENCY
When a read request is made, Object Storage always serves the most recent copy of the data that was written to the system.
DURABILITY
Object Storage is a regional service. Data is stored redundantly across multiple storage servers. Object Storage actively monitors data integrity using checksums and automatically detects and repairs corrupt data. Object Storage actively monitors and ensures data redundancy. If a redundancy loss is detected, Object Storage automatically creates more data copies. For more details about Object Storage durability, see the Oracle Cloud Infrastructure Object Storage FAQ.
CUSTOM METADATA
You can define your own extensive metadata as key-value pairs for any purpose. For example, you can create descriptive tags for objects, retrieve those tags, and sort through the data. You can assign custom metadata to objects and buckets using the Oracle Cloud Infrastructure CLI or SDK. See Software Development Kits and Command Line Interface for details.
ENCRYPTION
Object Storage employs 256-bit Advanced Encryption Standard (AES-256) to encrypt object data on the server. Each object is encrypted with its own key. Data encryption keys are encrypted with a master encryption key that is frequently rotated. Encryption is enabled by default and cannot be turned off.

References:
https://blogs.oracle.com/cloud-infrastructure/announcing-instance-principals-for-identity-
andaccess-management

Access to Your On-Premises Network There are two ways to connect your on-premises network to Oracle Cloud Infrastructure: VPN Connect: Offers multiple IPSec tunnels between your existing network's edge and your VCN, by way of a DRG that you create and attach to your VCN.
Oracle Cloud Infrastructure FastConnect: Offers a private connection between your existing network's edge and Oracle Cloud Infrastructure. Traffic does not traverse the internet. Both private peering and public peering are supported. That means your on-premises hosts can access private IPv4 addresses in your VCN as well as regional public IPv4 addresses in Oracle Cloud Infrastructure (for example, Object Storage or public load balancers in your VCN).
You can use one or both types of the preceding connections. If you use both, you can use them simultaneously, or in a redundant configuration. These connections come to your VCN by way of a single DRG that you create and attach to your VCN. Without that DRG attachment and a route rule for the DRG, traffic does not flow between your VCN and on-premises network. At any time, you can detach the DRG from your VCN but maintain all the remaining components that form the rest of the connection. You could then reattach the DRG again, or attach it to another VCN.

References:
https://docs.cloud.oracle.com/iaas/Content/Compute/References/bestpracticescompute.htm
System Resilience Oracle Cloud Infrastructure runs on Oracle's high-quality Sun servers. However, any hardware can experience a failure. Follow industry-wide hardware failure best practices to ensure the resilience of your solution. Some best practices include: Design your system with redundant compute nodes in different availability domains to support fail-over capability. Create a custom image of your system drive each time you change the image. Back up your data drives, or sync to spare drives, regularly. If you experience a hardware failure and have followed these practices, you can terminate the failed instance, launch your custom image to create a new instance, and then apply the backup data.

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.

you may optionally specify one or more security lists for the subnet to use (up to five). If you don't specify any, the subnet uses the cloud network's default security list. You can change which security list the subnet uses at any time.
https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/managingVCNs.htm

References:
https://docs.cloud.oracle.com/en-us/iaas/Content/Database/Tasks/exausingdataguard.htm

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/Compute/Tasks/launchinginstance.htm

References:
Overview of Data Transfer Service Oracle offers offline data transfer solutions that let you migrate data to Oracle Cloud Infrastructure. Moving data over the public internet is not always feasible due to high network costs, unreliable network connectivity, long transfer times, and security concerns. Our transfer solutions address these pain points, are easy to use, and provide significantly faster data upload compared to over-the-wire data transfer. (https://docs.cloud.oracle.com/iaas/Content/DataTransfer/Concepts/overview.htm)

References:
https://oracle.github.io/learning-library/oci-library/L100-LAB/Autonomous_Data_Warehouse/ADW_HOL.html

in ADW, The tnsnames.ora file provided with the credentials zip file contains three database service names identifiable as high, medium, and low. The predefined service names provide different levels of performance and concurrency for Autonomous Data Warehouse. high: The High database service provides the highest level of resources to each SQL statement resulting in the highest performance, but supports the fewest number of concurrent SQL statements. Any SQL statement in this service can use all the CPU and IO resources in your database. The number of concurrent SQL statements that can be run in this service is 3, this number is independent of the number of OCPUs in your database. medium: The Medium database service provides a lower level of resources to each SQL statement potentially resulting a lower level of performance, but supports more concurrent SQL statements. Any SQL statement in this service can use multiple CPU and IO resources in your database. The number of concurrent SQL statements that can be run in this service depends on the number of OCPUs in your database. low: The Low database service provides the least level of resources to each SQL statement, but supports the most number of concurrent SQL statements. Any SQL statement in this service can use a single CPU and multiple IO resources in your database. The number of concurrent SQL statements that can be run in this service can be up to 300 times the number of OCPUs. The predefined service names provide different levels of performance and concurrency for Autonomous DB
Choose whichever database service offers the best balance of performance and concurrency. Use the low database service name. to minimize the impact of their SQLs to by low consumer group

https://docs.cloud.oracle.com/iaas/Content/Object/Tasks/usingpreauthenticatedrequests.htm
You can create an unlimited number of pre-authenticated requests. You can't edit a pre-authenticated request. If you want to change user access options in response to changing requirements, you must create a new
pre-authenticated request. URL:
https://docs.cloud.oracle.com/iaas/Content/Object/Tasks/
managingbuckets.htm You can change a bucket's access from public to private or from private to public.
Changing the type of access doesn't affect existing pre-authenticated requests. Existing pre-authenticated requests still work.

References:
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.

References:
https://cloud.oracle.com/iaas/whitepapers/best-practices-for-iam-on-oci.pdf
You manage the following types of credentials with Oracle Cloud Infrastructure IAM: Console password: For signing in to the Console, which is the user interface for interacting with Oracle Cloud Infrastructure API signing key (in PEM format): For sending API requests, which require authentication Swift password: For using a Swift client with Recovery Manager (RMAN) to back up an Oracle Database System (DB System) database to Object Storage

References:
After you create a load balancer, you can apply policies to control traffic distribution to your backend servers. The Load Balancing service supports three primary policy types: Round Robin Least Connections
IP Hash

The Oracle Cloud Infrastructure Block Volume service lets you expand the size of block volumes and boot volumes. You have three options to increase the size of your volumes: Expand an existing volume in place with offline resizing. See Resizing a Volume Using the Console for the steps to do this.
Restore from a volume backup to a larger volume. See Restoring a Backup to a New Volume and Restoring a Boot Volume.
Clone an existing volume to a new, larger volume. See Cloning a Volume and Cloning a Boot Volume.

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

a policy statement must specify the compartment for which access is being granted (or the tenancy).
Where you create the policy determines who can update the policy. If you attach the policy to the compartment or its parent, you can simply specify the compartment name. If you attach the policy further up the hierarchy, you must specify the path. The format of the path is each compartment name (or OCID) in the path, separated by a colon:
<compartment_level_1>:<compartment_level_2>: . . . <compartment_level_n> For example, assume you have a three-level compartment hierarchy, shown here:

You want to create a policy to allow NetworkAdmins to manage VCNs in CompartmentC. If you want to attach this policy to CompartmentC or to its parent, CompartmentB, write this policy statement: Allow group NewtworkAdmins to manage virtual-network-family in compartment CompartmentC.
However, if you want to attach this policy to CompartmentA (so that only administrators of CompartmentA can modify it), write this policy statement that specifies the path: Allow group NewtworkAdmins to manage virtual-network-family in compartment CompartmentB:CompartmentC
To attach this policy to the tenancy, write this policy statement that specifies the path from CompartmentA to CompartmentC: Allow group NewtworkAdmins to manage virtual-network-family in compartment CompartmentA:CompartmentB:CompartmentC

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.