Oracle 1z0-1072-23 Oracle Cloud Infrastructure 2023 Architect Associate Exam Practice Test

 You can change the block volume size when cloning a volume. The explanation is that cloning a volume is a way of creating an exact copy of an existing volume without creating a backup first. Cloning a volume is faster and cheaper than creating a backup and restoring it to a new volume. When you clone a volume, you can change the block volume size, performance, encryption settings, and tags of the new volume. You do not need to detach a volume before cloning it, as cloning does not affect the source volume or its attachments. You cannot clone a volume to another region, as cloning only works within the same region and availability domain. Creating a clone usually takes less time than creating a backup of a volume, as cloning does not involve transferring data to Object Storage.

Dimensions and Grouping Function are two optional components while creating the Monitoring Query Language (MQL) expressions in the OCI Monitoring service. Dimensions are key-value pairs that provide additional information about a metric, such as region, compartment, or resource type. Grouping Function is a function that aggregates metric data across one or more dimensions, such as sum, count, or average. The other options are required components for MQL expressions. References: [Dimensions], [Grouping Function]

Group the boot volumes into a volume group and create a custom backup policy. Group the block volumes and create a custom backup policy. The explanation is that volume groups are logical collections of block volumes and boot volumes that can be backed up together as a consistent point-in-time snapshot. You can create a custom backup policy for each volume group and specify the frequency and retention period of the backups. This way, you can meet different backup requirements for different types of volumes.

If you choose not to proactively reboot the instance before the scheduled maintenance due date, the instance is either reboot-migrated or rebuilt in place for you. Reboot-migration is a process where OCI migrates your instance to a new physical host without changing its configuration or public IP address. Rebuild in place is a process where OCI shuts down your instance, performs maintenance on the physical host, and restarts your instance with the same configuration and public IP address. The other options are not correct. References: [Reboot-Migration], [Rebuild in Place]

While a multipart upload is still active, you can keep adding parts as long as the total number is less than 10,000. When you split the object into individual parts, each part can be as large as 50 GiB. The explanation is that a multipart upload allows you to upload a large object in parts, which can improve performance and reliability. You need to split the object into parts yourself and upload each part separately using the Multipart Upload API. You can add parts to an active multipart upload until you reach the maximum number of 10,000 parts per upload. Each part can range from 10 MiB to 50 GiB in size, except for the last part, which can be any size.

Even if nothing has changed within the file system since the last snapshot was taken, a new snapshot does not consume more storage. This is because snapshots are incremental and only store the changes made to the file system since the previous snapshot. The other statements are correct regarding the OCI File System snapshots. References: [Snapshots and Storage Consumption]

Audit is the OCI service that would help identify the details of all users who were active in the last six hours along with any REST API calls that were executed. Audit is a service that records all API calls and other actions taken by or on behalf of users in OCI. It can be used to track user activity, monitor compliance, and troubleshoot issues. The other options are not suitable for this task. References: [Audit]

Attaching a block volume to an instance in a different availability domain is not a valid action within the OCI Block Volume service. A block volume can only be attached to an instance in the same availability domain. The other options are valid actions that can be performed with the Block Volume service. References: [Block Volume Actions]

According to the Oracle Cloud Infrastructure documentation1, autoscaling enables you to automatically adjust the number of compute instances in an instance pool based on performance metrics such as CPU and memory utilization. You select a performance metric to monitor and set thresholds that the performance metric must reach to trigger an autoscaling event. When system usage meets a threshold, autoscaling dynamically resizes the instance pool in near-real time. As load increases, the pool scales out. As load decreases, the pool scales in.

Therefore, option B is the correct answer, as it allows you to monitor the memory usage of your application and scale up the number of instances when it meets or exceeds a predefined threshold. This will prevent poor application performance due to insufficient memory.

Allow group NetworkAdmins to manage virtual-network-family in compartment A:B:C. The explanation is that when you attach a policy to the tenancy, you need to specify the full path of the compartment where you want to grant permissions. In this case, the compartment C is a sub-compartment of compartment B, which is a sub-compartment of compartment A, which is a sub-compartment of the root compartment (tenancy). Therefore, the full path of compartment C is A:B:C. The virtual-network-family resource type includes all the resources related to VCN, such as subnets, route tables, security lists, gateways, etc.

Exadata Virtual Machine is not a valid option for an OCI compute shape. Exadata Virtual Machine is a deployment option for Exadata Cloud Service or Exadata Cloud@Customer, which are services that provide dedicated Exadata infrastructure for running Oracle databases in OCI. Exadata Virtual Machine allows you to create multiple virtual machines on each Exadata compute node and isolate them from each other using Oracle VM technology. The valid options for OCI compute shapes are:

• Bare Metal: A bare metal instance is a physical server that gives you direct access to the underlying hardware and full isolation from other tenants.
• Dedicated Virtual Machine Host: A dedicated virtual machine host is a physical server that hosts only your virtual machine instances and no other tenant’s instances.
• Virtual Machine: A virtual machine instance is a virtual server that runs on a shared physical server with other tenants’ instances.
• Burstable: A burstable instance is a virtual machine instance that has a baseline utilization of either 12% or 50% of each CPU core and can burst above the baseline when needed.

Oracle Security Zones is a service that helps you enforce best practices and prevent misconfigurations on your OCI resources by applying predefined policies and controls. Some of the benefits of using Security Zones are:

• Encrypt storage resources with a customer-managed key: Security Zones require that all storage resources, such as block volumes, boot volumes, file systems, and object storage buckets, are encrypted with a customer-managed key from Vault. This ensures that you have full control over the encryption and decryption of your data at rest.
• Deny public access to OCI resources, such as databases and object storage buckets: Security Zones prevent you from creating or updating OCI resources that have public access enabled, such as databases and object storage buckets that are accessible from the internet. This reduces the risk of unauthorized access or data leakage.

The explanation is that the Infrequent Access tier is suitable for storing data that is accessed less frequently but requires immediate access when needed. The Infrequent Access tier has lower storage costs than the Standard tier, but higher retrieval costs. The Infrequent Access tier also has a minimum storage duration of 30 days, which means that you will be charged for at least 30 days of storage even if you delete or move the data before that period.

The explanation is that burstable instances are VM instances that have a baseline utilization of either 12% or 50% of each CPU core, not 25% or 75%. Burstable instances are designed for scenarios where an instance is typically idle or has low CPU utilization but occasionally needs to burst above the baseline to handle spikes in demand. Burstable instances cost less than regular instances with the same total OCPU count but charge extra for bursting above the baseline OCPU.