Q2 Question 34 Explanation

Not all migration methods apply to all migration scenarios. Many of the migration methods apply only if specific characteristics of the source and destination databases match or are compatible. Moreover, additional factors can affect which method you choose for your migration from among the methods that are technically applicable to your migration scenario.

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

On-premises database version

Database service database version

On-premises host operating system and version

On-premises database character set

Quantity of data, including indexes

Data types used in the on-premises database

Storage for data staging

Acceptable length of system outage

Network bandwidth

Read More

Q2 Question 33 Explanation

Oracle Cloud Infrastructure Streaming

OCI Streaming service provides a fully managed, scalable, durable storage option for continuous, high-volume streams of data that you can consume and process in real-time

Use cases

Streaming can be used for messaging, ingesting high volume data such as application log data, operational telemetry data, web click-stream data or other use cases in which data is produced and processed continually and sequentially in a publish-subscribe messaging model.

Messaging: Use streaming as a backplane to decouple components of large systems. Key-scoped ordering, low latency and guaranteed durability of streaming provide reliable primitives to implement a variety of messaging patterns, while high throughput potential allows for such a system to scale well.

Web/Mobile activity data ingestion: Use streaming as your ingestion pipeline for usage data from web sites or mobile apps (such as page views, searches, or other actions users may take). Streaming’s consumer model makes it easy to feed information to multiple real-time monitoring and analytics systems or to a data warehouse for offline processing and reporting.

Metric and log ingestion: Use streaming as an alternative for traditional log and metrics aggregation approaches to help make critical operational data more quickly available for indexing, analysis, and visualization.

Infrastructure and application event processing: Use streaming as a unified entry point for cloud components to report their life cycle events for audit, accounting, and related activities.

Read More

Q2 Question 32 Explanation

You can change the shape of a virtual machine (VM) instance without having to rebuild your instances or redeploy your applications. This lets you scale up your Compute resources for increased performance, or scale down to reduce cost.

When you change the shape of an instance, you select a different processor, number of cores, amount of memory, network bandwidth, and maximum number of VNICs for the instance. The instance's public and private IP addresses, volume attachments, and VNIC attachments remain the same.

Read More

Q2 Question 31 Explanation

Object Lifecycle Management works by defining rules that instruct Object Storage to archive or delete objects on your behalf within a given bucket. A bucket's lifecycle rules are collectively known as an object lifecycle policy.

You can use a rule to either archive or delete objects and specify the number of days until the specified action is taken.

A rule that deletes an object always takes priority over a rule that would archive that same object.

Read More

Q2 Question 30 Explanation

in Transit routing through a private IP in the VCN you set up an instance in the VCN to act as a firewall or intrusion detection system to filter or inspect the traffic between the on-premises network and Oracle Services Network.

The Networking service lets you implement network security functions such as intrusion detection, application-level firewalls

In fact, the IDS model can be host-based IDS (HIDS) or network-based IDS (NIDS). HIDS is installed at a host to periodically monitor specific system logs for patterns of intrusions. In contrast, an NIDS sniffs the traffic to analyze suspicious behaviors. A signature-based NIDS (SNIDS) examines the traffic for patterns of known intrusions. SNIDS can quickly and reliably diagnose the attacking techniques and security holes without generating an over-whelming number of false alarms because SNIDS relies on known signatures. However, anomaly-based NIDS (ANIDS) detects unusual behaviors based on statistical methods. ANIDS could detect symptoms of attacks without specific knowledge of details. However, if the training data of the normal traffic are inadequate, ANIDS may generate a large number of false alarms.

Read More

Q2 Question 29 Explanation

Oracle Functions is a fully managed, multi-tenant, highly scalable, on-demand, Functions-as-a-Service platform. It is built on enterprise-grade Oracle Cloud Infrastructure and powered by the Fn Project open source engine. Use Oracle Functions (sometimes abbreviated to just Functions) when you want to focus on writing code to meet business needs.

Oracle Cloud Infrastructure Container Engine for Kubernetes is a fully-managed, scalable, and highly available service that you can use to deploy your containerized applications to the cloud. Use Container Engine for Kubernetes (sometimes abbreviated to just OKE) when your development team wants to reliably build, deploy, and manage cloud-native applications. You specify the compute resources that your applications require, and Container Engine for Kubernetes provisions them on Oracle Cloud Infrastructure in an existing OCI tenancy.

Read More

Q2 Question 28 Explanation

Federating with Microsoft Azure Active Directory

To federate with Azure AD, you set up Oracle Cloud Infrastructure as a basic SAML single sign-on application in Azure AD. To set up this application, you perform some steps in the Oracle Cloud Infrastructure Console and some steps in Azure AD.

Following is the general process an administrator goes through to set up the federation. Details for each step are given in the next section.

In Oracle Cloud Infrastructure, download the federation metadata document.

In Azure AD, set up Oracle Cloud Infrastructure Console as an enterprise application.

In Azure AD, configure the Oracle Cloud Infrastructure enterprise application for single sign-on.

In Azure AD, set up the user attributes and claims.

In Azure AD, download the Azure AD SAML metadata document.

In Azure AD, assign user groups to the application.

In Oracle Cloud Infrastructure, set up Azure AD as an identity provider.

In Oracle Cloud Infrastructure, map your Azure AD groups to Oracle Cloud Infrastructure groups.

In Oracle Cloud Infrastructure, set up the IAM policies to govern access for your Azure AD groups.

Share the Oracle Cloud Infrastructure sign-in URL with your user

Read More

Q2 Question 27 Explanation

Oracle Cloud Infrastructure Vault lets you centrally manage the encryption keys that protect your data and the secret credentials that you use to securely access resources. You can use the Vault service to create and manage the following resources:

Vaults

Keys

Secrets

Vaults securely store master encryption keys and secrets that you might otherwise store in configuration files or in code.

The Vault service lets you create vaults in your tenancy as containers for encryption keys and secrets. If needed, a virtual private vault provides you with a dedicated partition in a hardware security module (HSM), offering a level of storage isolation for encryption keys that’s effectively equivalent to a virtual independent HSM.

Read More

Q2 Question 26 Explanation

you can monitor the health, capacity, and performance of functions you've deployed to Oracle Functions by using metrics

Oracle Functions monitors function execution, and collects and reports metrics such as:

The number of times a function is invoked.

The length of time a function runs for.

The number of times a function failed.

The number of requests to invoke a function that returned a '429 Too Many Requests' error in the response (known as 'throttled function invocations').

Read More

Q2 Question 25 Explanation

You can define the members of the dynamic group based on the following:

- compartment ID

- instance ID

- tag namespace and tag key

- tag namespace, tag key, and tag value

Supported variables are:

instance.compartment.id - the OCID of the compartment where the instance resides

instance.id - the OCID of the instance

tag.<tagnamespace>.<tagkey>.value - the tag namespace and tag key. For example, tag.department.operations.value.

tag.<tagnamespace>.<tagkey>.value='<tagvalue>' - the tag namespace, tag key, and tag value. For example, tag.department.operations.value='45'

Read More

Q2 Question 24 Explanation

Migrating an On-Premises Database to Oracle Cloud Infrastructure by Creating a Backup in the Cloud

You can migrate an on-premises database to Oracle Cloud Infrastructure by creating a backup of your on-premises database in Oracle Cloud Infrastructure's Database service.

Oracle provides a Python script to create a backup of your database. The script invokes an API call to create the backup and then places the backup in Oracle Cloud Infrastructure. You can then use the Console or the API to create a new database or DB system from that backup. Backups created using the instructions in this topic appear under Standalone Backups in the console.

The Python script is bundled as a part of the Oracle Cloud Infrastructure CLI installation. Oracle provides the migration script and associated files at no cost. Normal Object Storage charges apply for the storage of your backup in Oracle Cloud Infrastructure.

Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud

You can migrate Oracle Database 12c non-CDB databases from on-premises to Oracle Database 12c databases in Oracle Cloud Infrastructure Database service using several different methods.

The applicability of some of the migration methods depends on the on-premises database’s character set and platform endian format.

If you have not already done so, determine the database character set of your on-premises database, and determine the endian format of the platform your on-premises database resides on. Use this information to help you choose an appropriate method.

Data Pump Conventional Export/Import

This method can be used regardless of the endian format and database character set of the on-premises database.

For the steps this method entails, see Data Pump Conventional Export/Import.

Data Pump Transportable Tablespace

This method can be used only if the on-premises platform is little endian, and the database character sets of your on-premises database and the Database database are compatible.

For the steps this method entails, see Data Pump Transportable Tablespace.

RMAN Transportable Tablespace with Data Pump

This method can be used only if the on-premises platform is little endian, and the database character sets of your on-premises database and the Database service database are compatible.

For the steps this method entails, see RMAN Transportable Tablespace with Data Pump.

RMAN CONVERT Transportable Tablespace with Data Pump

This method can be used only if the database character sets of your on-premises database and the Database service database are compatible.

This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Database service platform is little-endian format.

For the steps this method entails, see RMAN CONVERT Transportable Tablespace with Data Pump.

RMAN Cross-Platform Transportable Tablespace Backup Sets

This method can be used only if the database character sets of your on-premises database and the Database database are compatible.

For the steps this method entails, see RMAN Cross-Platform Transportable Tablespace Backup Sets.

Data Pump Full Transportable

This method can be used only if the database character sets of your on-premises database and the Database service database are compatible.

For the steps this method entails, see Data Pump Full Transportable.

Unplugging/Plugging (non-CDB)

This method can be used only if the on-premises platform is little endian, and the on-premises database and Database service database have compatible database character sets and national character sets.

You can use the unplug/plug method to migrate an Oracle Database 12c non-CDB database to Oracle Database 12c in the cloud. This method provides a way to consolidate several non-CDB databases into a single Oracle Database 12c CDB on the cloud.

For the steps this method entails, see Unplugging/Plugging Non-CDB.

Remote Cloning (non-CDB)

This method can be used only if the on-premises platform is little endian, the on-premises database release is 12.1.0.2 or higher, and the on-premises database and Database service database have compatible database character sets and national character sets.

You can use the remote cloning method to copy an Oracle Database 12c non-CDB on-premises database to your Oracle Database 12c database in the cloud.

For the steps this method entails, see Remote Cloning Non-CDB.

SQL Developer and SQL*Loader to Migrate Selected Objects

You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL*Loader to load the data into your cloud database.

For the steps this method entails, see SQL Developer and SQL*Loader to Migrate Selected Objects.

SQL Developer and INSERT Statements to Migrate Selected Objects

You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL INSERT statements to load the data into your cloud database.

For the steps this method entails, see SQL Developer and INSERT Statements to Migrate Selected Objects.

Read More

Q2 Question 23 Explanation

STEERING POLICIES is A framework to define the traffic management behavior for your zones. Steering policies contain rules that help to intelligently serve DNS answers.

FAILOVER

Failover policies allow you to prioritize the order in which you want answers served in a policy (for example, Primary and Secondary). Oracle Cloud Infrastructure Health Checks are leveraged to determine the health of answers in the policy. If the Primary Answer is determined to be unhealthy, DNS traffic will automatically be steered to the Secondary Answer.

LOAD_BALANCE

Load Balancer policies allow distribution of traffic across multiple endpoints. Endpoints can be assigned equal weights to distribute traffic evenly across the endpoints or custom weights may be assigned for ratio load balancing. Oracle Cloud Infrastructure Health Checks are leveraged to determine the health of the endpoint. DNS traffic will be automatically distributed to the other endpoints, if an endpoint is determined to be unhealthy.

ROUTE_BY_GEO

Geolocation-based steering policies distribute DNS traffic to different endpoints based on the location of the end user. Customers can define geographic regions composed of originating continent, countries or states/provinces (North America) and define a separate endpoint or set of endpoints for each region.

ROUTE_BY_ASN

ASN-based steering policies enable you to steer DNS traffic based on Autonomous System Numbers (ASN). DNS queries originating from a specific ASN or set of ASNs can be steered to a specified endpoint.

ROUTE_BY_IP

IP Prefix-based steering policies enable customers to steer DNS traffic based on the IP Prefix of the originating query.

Read More

Q2 Question 22 Explanation

Subnet or VCN Deletion

To delete a VCN, it must first be empty and have no related resources or attached gateways

To delete a VCN's subnets, they must first be empty.

Note:

When you create one of the preceding resources, you specify a VCN and subnet for it. The relevant service creates at least one VNIC in the subnet and attaches the VNIC to the resource. The service manages the VNICs on your behalf, so they are not readily apparent to you in the Console. The VNIC enables the resource to communicate with other resources over the network. Although this documentation commonly talks about the resource itself being in the subnet, it's actually the resource's attached VNIC.

If the subnet is not empty, you instead get an error indicating that there are still resources that you must delete first. The error includes the OCID of a VNIC that is in the subnet (there could be more, but the error returns only a single VNIC's OCID).

You can use the Oracle Cloud Infrastructure command line interface (CLI) or another SDK or client to call the GetVnic operation with the VNIC OCID. The response includes the VNIC's display name. Depending on the type of parent resource, the display name can indicate which parent resource the VNIC belongs to. You can then delete that parent resource, or you can contact your administrator to determine who owns the resource. When the VNIC's parent resource is deleted, the attached VNIC is also deleted from the subnet. If there are remaining VNICs in the subnet, repeat the process of determining and deleting each parent resource until the subnet is empty. Then you can delete the subnet.

For example, if you're using the CLI, use this command to get information about the VNIC.

oci network vnic get --vnic-id <VNIC_OCID

Read More