Free 1Z0-1072-21 Exam Dumps Preview

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

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.

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.

https://docs.cloud.oracle.com/iaas/Content/Balance/Tasks/managingloadbalancer.htm?tocpath=Services%7CLoad%20Balancing%7C_____5Theessentialcomponentsforloadbalancinginclude:?Aloadbalancerwithpre-provisionedbandwidth.?Abackendsetwithahealthcheckpolicy.SeeManagingBackendSets.?Backendserversforyourbackendset.SeeManagingBackendServers.?Oneormorelisteners.SeeManagingLoadBalancerListeners.?Loadbalancersubnetsecurityrulestoallowtheintendedtraffic.Tolearnmoreaboutthese
rules, see Security Rules.
?Optionally, you can associate your listeners with SSL server certificate bundles to manage how your system handles SSL traffic. See Managing SSL Certificates

References:
https://docs.cloud.oracle.com/en-us/iaas/Content/Audit/Reference/logeventreference.htm#payload

References:
Oracle Cloud Infrastructure supports federation with Oracle Identity Cloud Service and Microsoft Active Directory (via Active Directory Federation Services (AD FS)), and any identity provider that supports the Security Assertion Markup Language (SAML) 2.0 protocol.

When creating a compartment, you must provide a name for it (maximum 100 characters, including letters, numbers, periods, hyphens, and underscores) that is unique within its parent compartment. You must also provide a description, which is a non-unique, changeable description for the compartment, from 1 through
400 characters.
After creating a compartment, you need to write at least one policy for it, otherwise no one can access it (except administrators or users who have permissions set at the tenancy level). When creating a compartment inside another compartment, the compartment inherits access permissions from compartments higher up its hierarchy.
When you create an access policy, you need to specify which compartment to attach it to. This controls who can later modify or delete the policy. Depending on how you've designed your compartment hierarchy, you might attach it to the tenancy, a parent, or to the specific compartment itself.

The mount target provides the IP address or DNS name that is used together with a unique export path to mount the file system.
You can move mount targets from one compartment to another.

References:
https://blogs.oracle.com/cloud-infrastructure/introducing-oracle-cloud-infrastructure-data-transfer-
service

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

Autonomous Transaction Processing comes with predefined CPU/IO shares assigned to different consumer groups. You can modify these predefined CPU/IO shares if your workload requires different
CPU/IO resource allocations.
By default, the CPU/IO shares assigned to the consumer groups TPURGENT, TP, HIGH, MEDIUM, and LOW are 12, 8, 4, 2, and 1, respectively. The shares determine how much CPU/IO resources a consumer group can use with respect to the other consumer groups. With the default settings the consumer group TPURGENT will be able to use 12 times more CPU/IO resources compared to LOW, when needed. The consumer group TP will be able to use 4 times more CPU/IO resources compared to MEDIUM, when needed.

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

All databases created in Oracle Cloud Infrastructure are encrypted using transparent data encryption (TDE).
Oracle Cloud Infrastructure encrypts all managed backups in the object store. Oracle uses the Database Transparent Encryption feature by default for encrypting the backups. and the customers can manage the TDE Wallet after DB Systems are provisioned.

Identity > Compartments >(The root Compartment of the tenancy)

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

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

References:
https://docs.oracle.com/en/solutions/migrate-to-atp/index.html#GUID-28E5A683-6DC6-4A07-
BB1C-55F020D4C1CD

References:
https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/managingdynamicgroups.htm

https://docs.cloud.oracle.com/iaas/Content/Balance/Tasks/managingcertificates.htm

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

When Autonomous Databas instance is stopped, CPU billing is halted based on full-hour cycles of usage Billing for storage continues as long as the service instance exists. and When Autonomous Database instance is started, the CPU billing is initiated

Oracle Cloud Infrastructure File Storage service provides a durable, scalable, secure, enterprise-grade network file system. You can connect to a File Storage service file system from any bare metal, virtual machine, or container instance in your Virtual Cloud Network (VCN). You can also access a file system from outside the VCN using Oracle Cloud Infrastructure FastConnect and Internet Protocol security (IPSec) virtual private network (VPN).
EXPORT
Exports control how NFS clients access file systems when they connect to a mount target. File systems are exported (made available) through mount targets. Each mount target maintains an export set which contains one or many exports. A file system must have at least one export in one mount target in order for instances to mount the file system. The information used by an export includes the file system OCID, mount target OCID, export set OCID, export path, and client export options. For more information, see Managing Mount Targets.
EXPORT SET
Collection of one or more exports that control what file systems the mount target exports using NFSv3 protocol and how those file systems are found using the NFS mount protocol. Each mount target has an export set. Each file system associated with the mount target has at least one export in the export set.
EXPORT PATH
A path that is specified when an export is created. It uniquely identifies the file system within the mount target, letting you associate up to 100 file systems to a single mount target. This path is unrelated to any path within the file system itself, or the client mount point path.
EXPORT OPTIONS NFS export options are a set of parameters within the export that specify the level of access granted to NFS clients when they connect to a mount target. An NFS export options entry within an export defines access for a single IP address or CIDR block range. For more information, see Working with NFS Export Options.

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.

https://docs.cloud.oracle.com/iaas/Content/GSG/Concepts/baremetalintro.htm

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.

Dynamic groups allow you to group Oracle Cloud Infrastructure computer instances as "principal" actors (similar to user groups).
When you create a dynamic group, rather than adding members explicitly to the group, you instead define a set of matching rules to define the group members. For example, a rule could specify that all instances in a particular compartment are members of the dynamic group. The members can change dynamically as instances are launched and terminated in that compartment. A dynamic group has no permissions until you write at least one policy that gives that dynamic group permission to either the tenancy or a compartment.
When writing the policy, you can specify the dynamic group by using either the unique name or the dynamic group's OCID. Per the preceding note, even if you specify the dynamic group name in the policy, IAM internally uses the OCID to determine the dynamic group.

Setting Up a Remote Peering Create the RPCs: Each VCN administrator creates an RPC for their own VCN's DRG. Share information: The administrators share the basic required information. Set up the required IAM policies for the connection: The administrators set up IAM policies to enable the connection to be established.
Establish the connection: The requestor connects the two RPCs (see Important Remote Peering Concepts for the definition of the requestor and acceptor). Update route tables: Each administrator updates their VCN's route tables to enable traffic between the peered VCNs as desired.
Update security rules: Each administrator updates their VCN's security rules to enable traffic between the peered VCNs as desired.