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

The MEDIUM and LOW consumer group can run up to 16 concurrent SQL statements if HIGH consumer group has 0 SQL statements

The HIGH consumer group can run up to 16 concurrent SQL statements as long as MEDIUM and LOW consumer groups have 0 SQL statements

The MEDIUM consumer group can run 20 concurrent SQL statements when HIGH consumer group has 0 SQL statements

The HIGH consumer group can run up to 16 concurrent SQL statements in addition to 32 concurrent SQL statements in MEDIUM and LOW consumer group each

The HIGH consumer group can run 3 concurrent SQL statements when MEDIUM consumer group has 0 SQL statements

Instruct the Operations team to reassign the custom image to the Finance compartment so you can select it from a drop-down list when launching new compute resources.

Instruct the Operations team to export the image to an object storage bucket, create a pre-authenticated request (PAR), and provide you with the URL. Download the custom image to your laptop and import it as a custom image in the Finance compartment.

Instruct the Administrators team to grant you access to use instance-images in the Operations compartment. Use the Oracle Cloud Identifier (OCID) of the custom image when launching new compute resources in the Finance compartment.

Instruct the Operations team to export the image to an object storage bucket, create a PAR, and provide you with the URL. Use that URL as the source when importing a custom image. Import the custom image into the Finance compartment.

Instruct the Operations team to export the image to an object storage bucket. Instruct the Administrators team to grant you access to the object storage bucket where the custom image is stored. Use the download URL of the custom image as the image source when launching new compute resources in the Finance compartment.

A database name cannot be used concurrently for both an Autonomous Data Warehouse (ADW) and an ATP database

After terminating a database, the database name is available for immediate reuse

A maximum of 8 cores can be enabled for an ATP database

A maximum of 2 TB of storage can be enabled for an ATP database

Data Guard as a Service is offered between regions.

You cannot manage the database as sys/sysdba.

You have full control over the automatic backup schedule and retention periods.

You can manage Oracle database initialization parameters at a global level.

Create a new IAM group in OCI and map it to the existing IDCS group. Create a new policy in IDCS and reference the name of the IAM group.

Create a new Identity and Access Management (IAM) policy in OCI and reference the name of the IDCS group in each policy statement.

Create a new compartment in OCI with the same name as the existing IDCS group. Create an IAM policy that references the new compartment and the name of the IDCS group.

Create a new IAM group in OCI and map it to the existing IDCS group. Create a new IAM policy and reference the name of the IAM group in each policy statement.

Write an IAM policy and authorize the Object Storage service to manage objects on your behalf

Specify an existing destination bucket

Specify the bucket visibility for both the source and destination buckets

Provide a destination object name

Provide an option to choose bulk copying of objects

Choose an overwrite rule

Create Object Storage Lifecycle rules to archive objects from the legacy bucket after 365 days without any pattern matching

Create Object Storage Lifecycle rules to delete objects from the legacy bucket after 365 days with a filter type - include by pattern: ''.docx

It is not possible to meet this requirement

Create Object Storage Lifecycle rules to delete objects from the legacy bucket after 365 days with a filter type - exclude by pattern: ''.xlsx"

Create Object Storage Lifecycle rules to delete objects from the legacy bucket after 365 days without any pattern matching

Check security lists and route tables of your virtual cloud network (VCN) and fix any issues associated with the rules

Create separate listeners for each backend web server

Delete and re-create your OCI load balancer

Disable session persistence on your backend set

YAML

JSON

HCL

XML

It can be restored as new volumes to any Availability Domain within the same region.

It must be restored as new volumes to the same Availability Domain on which the original block volume backup resides.

It can be restored as new volumes to any Availability Domain across different regions.

It can be restored as new volumes with different sizes from the backups.

response body

URL path

timeout

port

status code

mytenancy.oc.ocid is a valid OCID.

If you delete a user, and them create a new user with the same name, the user will be considered a different user because of different OCIDs.

Users can customize OCIDs for all the resources in their compartments.

If you delete a user, and then create a new user with the same name, the new user will be assigned the exact same OCIDs as the system remembers.

load balancer

compute

database

block volumes

Groups

Users

Instances

Policies

VCNs

Oracle IAM controls which filesystems are mountable by which instances.

Security lists can be used as a virtual firewall to prevent an instance from mounting an FSS mount target within a subnet.

Encryption of file storage in FSS is optional.

Data in transit to an FSS mount target is encrypted.

FSS leverages UNIX user group and permission checking for file access security.

Object Storage on Oracle Cloud Infrastructure

ASM diskgroup

block volume

locally attached NVMe on Virtual Machine

You can have multiple subnets in an Availability Domain for a given VCN.

Private and Public subnets cannot reside in the same Availability Domain for a given VCN.

Subnets can have their IP addresses overlap with other subnets in another network for a given VCN.

Instances obtain their private IP and the associated security list from their subnets.

A custom resolver allows instances to use the host names of the hosts in your on-prem network that are connected to your VCN by an IPSec VPN connection.

A VCN resolver allows instances to use the host names of the hosts in your on-prem network that are connected to your VCN by an IPSec VPN connection.

A VCN resolver allows instances to use host names to communicate with instances on other VCNs in your tenancy.

An Internet resolver allows instances to use the host names that are published on the Internet.

You can launch a virtual or bare metal instance by using the same LaunchInstance API.

You cannot launch a bare metal server in Oracle Cloud Infrastructure Compute Service.

You can attach a block volume in an Availability Domain other than your compute instance.

You can share custom images across tenancies and regions.

The security lists of the subnets on which the two instances are located do not have “allow” rules for port 80 and 443.

The load balancer performed a health check on the application and found that compute instances were not in a healthy state and terminated the instances.

The client requested https access to the application and the load balancer service does not support end-to-end SSL from the client to the listener to the back-end set.

The Dynamic Routing Gateway is preventing the client traffic from your data center network from reaching the public IP of the load balancer.

Create a custom image of your system drive each time you change the image.

Attach block volumes from different Availability Domains to compute instances in different Availability Domains for high availability.

Design your system with redundant compute modes in different Availability Domains to support the failover capability.

Create backups of your block volumes that are associated with compute instances in different regions.

Disable cookie-based session persistence on your backend set.

Change keep-alive setting between the load balancer and backend server.

Disable SSL configuration associated with your backend set.

Create separate listeners for each backend web server.

Deploy production and DR applications in two separate virtual cloud networks (VCNs), each in different regions, and then use VCN local peering gateways for connectivity.

Deploy production and DR applications in two separate VCNs, each in different regions. Connect them using a VCN remote peering connection.

Deploy production and DR applications in the same VCN. Create production subnets in one AD, and DR subnets in another AD (assume a multi-AD region).

Deploy production and DR applications in two separate VCNs in different availability domains (ADs) within the primary region, and then use a VCN remote peering connection for connectivity.

Update the OS firewall in CLIENT-X to allow READ/WRITE access.

Update the security list TWO to restrict CLIENT-Y access to read-only.

Update the mount target export options to restrict CLIENT-Y access to read-only.

Update the security list ONE to restrict CLIENT-Y access to read only.

Add a new route rule to the private subnet route table to route default traffic to the internet gateway.

Attach a public IP address to the instances in the private subnet, and then add a new route rule to the

private subnet route table to route default traffic to the internet gateway.

Create a dynamic routing gateway (DRG) and attach it to your virtual cloud network (VCN). Add a default route rule to the private subnets route table and set the target as DRG.

Create a service gateway, add a new route rule to the private subnet route table that uses object storage as target type.

VCNs support transitive peering.

Peering VCNs should not have overlapping CIDR blocks.

VCNs must be in the same tenancy to be peered.

The only way to interconnect VCNs is through peering.

Terminate the instance while preserving the boot volume. Create a new instance from the boot volume and select a DenseIO shape to take advantage of local NVMe storage.

Create an object storage bucket and use a script that runs daily to move log files older than 15 days to the bucket.

Create and attach a block volume to the compute instance and copy the log files.

Create a custom image and launch a new compute instance with a larger boot volume size.

Write a custom script to remove the log files on a daily basis and free up the space on the boot volume.

Create a database user account for the business analyst.

Grant the predefined database role DWROLE to the database user.

Grant unlimited tablespace privilege to the database user.

Grant the predefined database role DWADW to the database user.

Grant the predefined database role DWUSER to the database user.

Terminate the compute instance preserving the boot volume. Create a new compute instance using the BM.GPU2.2 shape using the boot volume preserved, but no block volume attached.

Terminate the compute instance preserving the boot volume. Create a new compute instance using the VM.Standard2.2 shape using the boot volume preserved, but no block volume attached.

Terminate the compute instance preserving the boot volume. Create a new compute instance using the VM.GPU3.4 shape using the boot volume preserved and use the NVMe devices to host your application.

Terminate the compute instance preserving the boot volume. Create a new compute instance using the BM.HPC2.36 shape using the boot volume preserved and use the NVMe devices to host your application.

Terminate the compute instance preserving the boot volume. Create a new compute instance using the BM.GPU2.2 shape using the boot volume preserved and attach a new block volume to host your application.

Primary and standby databases must be in the same OCI region.

Both database systems must be in the same compartment.

Database systems need not be the same shape type (e.g, primary database can be a virtual machine, and standby database a bare metal shape, and vice versa).

Primary and standby database versions and editions need not be Identical.

Object storage resources can be shared across tenancies.

Immutable option for data stored in the Object Storage can be set via retention rules.

Object versioning is enabled at namespace level.

Object lifecycle rules can be used to either archive or delete objects.

Individual object parts can be as small as 10 MiB or as large as 50 GiB

While a multipart upload is still active, you cannot add parts even if the total number of parts is less than 10,000

The maximum size for an uploaded object is 10 TiB

You do not have to commit the upload after you have uploaded all the object parts

Load text files into ATP using SQL Developer.

Use RMAN duplicate.

Use Oracle Data Pump.

Transfer the physical database files and re-create the database.

Use database backup and restore.

Ensure that your database host can connect to OCI object storage.

Ensure the database archiving mode is set to NOARCHIVELOG.

Make sure that the database is not active and running while the backup is in progress.

Don't restart the dcsagent program even if it has a status of stop/waiting.