Oracle Cloud OCI 2023 Architect Associate 1Z0-1072-23 Part 1

Oracle Cloud Agent is a lightweight process that manages plugins running on compute instances. Which is NOT a valid Oracle Cloud Agent plugin name?

• Live Migration Agent

• OS Management Service Agent

• Compute Instance Run Command

• Bastion

Answer explanation

Live Migration Agent is not a valid Oracle Cloud Agent plugin name. Live migration refers to the process of moving a running virtual machine from one physical host to another without any disruption in service. While live migration can be performed in certain virtualization environments, it is not implemented as an Oracle Cloud Agent plugin.

You are part of a team that manages a set of workload instances running in an on-premises environment. The Architect team is tasked with designing and configuring the Oracle Cloud Infrastructure (OCI) Logging service to collect logs from these instances. There is a requirement to archive Info-level logging data of these instances into the OCI Object Storage.

Which TWO features of OCI can help you achieve this?

• Cloud Agent Plugin

• Grouping Function

• Service Connectors

• Agent Configuration

• ObjectCollectionRule

Answer explanation

To achieve the requirement of archiving Info-level logging data from on-premises instances into OCI Object Storage, we can use the following features of OCI:

1. Cloud Agent Plugin: The Cloud Agent Plugin is a lightweight software component that can be installed on the on-premises instances. It collects logs from these instances and sends them to the OCI Logging service. By configuring the Cloud Agent Plugin, we can ensure that logs are collected from the workload instances.

2. ObjectCollectionRule: The ObjectCollectionRule is a feature of OCI Logging service that allows us to define rules for collecting and storing logs in specific destinations, such as OCI Object Storage. We can create an ObjectCollectionRule specifically for Info-level logging data and configure it to store the logs in OCI Object Storage.

Therefore, by using both the Cloud Agent Plugin to collect logs from on-premises instances and configuring an ObjectCollectionRule to store Info-level logging data in OCI Object Storage, we can achieve the requirement mentioned in the question.

You create a file system and then add a 2 GB file. You then take a snapshot of the file system. What would be the total meteredBytes shown by the File Storage service after the hourly update cycle is complete?

• 3GB

• 2.5GB

• 4GB

• 2GB

Answer explanation

The total meteredBytes shown by the File Storage service after the hourly update cycle is complete would be 2.5 GB. This is because when you create a file system and add a 2 GB file, the initial size of the file system would be 2 GB. However, when you take a snapshot of the file system, it creates a copy of all the data in the file system at that point in time. So, in this case, taking a snapshot would increase the total size of the file system by an additional 0.5 GB (or 500 MB), resulting in a total size of 2.5 GB.

Which is NOT a valid statement regarding the Oracle Cloud Infrastructure (OCI) Audit service?

• Retention period for Audit logs is 365 days and it cannot be changed.

• Changes within the objects stored in an Object Storage bucket are collected as Audit logs.

• Audit service can record REST API calls executed by a custom client.

• Audit logs are displayed for Compartments.

Answer explanation

The statement that changes within the objects stored in an Object Storage bucket are collected as Audit logs is not a valid statement regarding the Oracle Cloud Infrastructure (OCI) Audit service. The OCI Audit service is designed to record and monitor activities related to resource management and access control within an OCI environment. It primarily focuses on tracking actions performed on resources such as compartments, users, groups, policies, etc. It does not specifically track changes made to objects stored in Object Storage buckets.

A few Object Storage buckets in your Oracle Cloud Infrastructure (OCI) tenancy should remain public, and yet you do not want the Cloud Guard service to detect these as problems. In which TWO ways would you address this requirement?

• Fix the base line by configuring Conditional Groups for the detector.

• Resolve or remediate those problems and you should not see Cloud Guard triggering on these resources ever again.

• Cloud Guard will keep detecting it because a public bucket is a security risk.

• Dismiss the problems associated with those resources.

Answer explanation

To address the requirement of having public Object Storage buckets in your OCI tenancy without triggering Cloud Guard, you can take the following steps:

A) Fix the baseline by configuring Conditional Groups for the detector: You can configure Conditional Groups in Cloud Guard to exclude specific resources or resource types from being considered as problems. By creating a Conditional Group that includes the public Object Storage buckets, you can prevent Cloud Guard from detecting them as security problems.

D) Dismiss the problems associated with those resources: Once you have identified the public Object Storage buckets as false positives or acceptable risks, you can dismiss or ignore the associated problems in Cloud Guard. This will prevent further triggering of alerts for those specific resources.

Option C is incorrect because it states that Cloud Guard will keep detecting public buckets as a security risk. While it is generally recommended to secure your resources and avoid making them publicly accessible, there may be valid use cases where certain Object Storage buckets need to remain public.

Option B is not a valid solution because resolving or remediating these "problems" would mean securing or making private those Object Storage buckets, which contradicts the requirement of keeping them public.

Therefore, options A and D are the correct ways to address this requirement.

You are part of an organization with thousands of users accessing Oracle Cloud Infrastructure (OCI). An unknown user action was executed resulting in configuration errors. You are tasked to quickly identify the details of all users who were active in the last six hours along with any REST API calls that were executed. Which OCI service would you use?

• Notifications

• Service Connectors

• Notifications

• Logging

• Audit

Answer explanation

The correct OCI service to use in this scenario is Audit.

The Audit service in Oracle Cloud Infrastructure (OCI) provides detailed logs and records of all user activities and API calls within the OCI environment. It allows you to track and monitor user actions, such as configuration changes, resource creation or deletion, and access control modifications.

By using the Audit service, you can quickly identify the details of all users who were active in the last six hours. It provides information about which users accessed the OCI environment during that time period.

Additionally, the Audit service also captures information about REST API calls that were executed by users. This means you can easily identify any specific API calls made by users within the specified timeframe.

Overall, by utilizing the Audit service in OCI, you can effectively investigate and analyze user activities to identify any potential configuration errors or unauthorized actions that may have occurred within your organization's infrastructure.

You have an instance running in Oracle Cloud Infrastructure (OCI) that cannot be live-migrated during an infrastructure maintenance event. OCI schedules a maintenance due date within 14 to 16 days and sends you a notification. What would happen if you choose not to proactively reboot the instance before the scheduled maintenance due date?

• The instance will get terminated.

• The instance is either reboot-migrated or rebuilt in place for you.

• You will receive another notification to reboot within the next 14 days.

• You will receive another notification to reboot within the next 7 days.

Answer explanation

If you choose not to proactively reboot the instance before the scheduled maintenance due date, Oracle Cloud Infrastructure (OCI) will take action on your behalf. The instance will either be reboot-migrated or rebuilt in place for you. This means that OCI will either move your instance to a different host while it is still running (reboot-migrate), or it will rebuild the instance on the same host without any downtime (rebuild in place). In both cases, OCI ensures that your instance remains operational during the maintenance event.

Which TWO components are optional while creating the Monitoring Query Language (MQL) expressions in the Oracle Cloud Infrastructure (OCI) Monitoring service?

• Interval

• Statistic

• Dimensions

• Grouping Function

• Metric

Answer explanation

1. Interval: The interval is a required component in MQL expressions. It specifies the time range for which the data should be retrieved or analyzed.

2. Statistic: The statistic is also a required component in MQL expressions. It defines the type of aggregation or calculation to be performed on the metric data, such as average, sum, maximum, minimum, etc.

3. Dimensions: Dimensions are optional components in MQL expressions. They allow you to filter and group the metric data based on specific attributes or properties associated with the resources being monitored.

4. Grouping Function: Grouping functions are also optional components in MQL expressions. They enable you to group and aggregate metric data based on specific criteria, such as grouping by resource type or region.

5. Metric: Although not mentioned in the question options, metrics are essential components of MQL expressions as they represent the actual measurements or observations being monitored.

Therefore, from the given options, Grouping Function and Dimensions are optional components while creating MQL expressions in OCI Monitoring service.

Which statement is NOT correct regarding the Oracle Cloud Infrastructure (OI) File System snapshots?

• Even if nothing has changed within the file system since the last snapshot was taken, a new snapshot consumes more storage.

• Snapshots are accessible under the root directory of the file system at .snapshot/name.

• Before you can clone a file system, at least one snapshot must exist for the file system.

• Snapshots are a consistent, point-in-time view of your file systems.

Answer explanation

The statement that "Even if nothing has changed within the file system since the last snapshot was taken, a new snapshot consumes more storage" is NOT correct regarding Oracle Cloud Infrastructure (OI) File System snapshots.

In reality, when a snapshot is taken in OI File System, it only captures the changes made to the file system since the previous snapshot. If nothing has changed within the file system since the last snapshot was taken, then taking a new snapshot will not consume any additional storage. The purpose of snapshots is to provide a point-in-time view of your file systems and only store incremental changes to save storage space.

You need to implement automatic backups for your database system. You can easily check “Enable Automatic Backup” in the web console. Before you do that though, you need to have which of the following TWO prerequisites in place?

• Access to the OCI Object Storage service

• Private SSH key to the database

• VCN configured with VPN for secure access to the Oracle Cloud Infrastructure (OCI) Object Storage service

• Connectivity to Swift endpoints

Answer explanation

The two prerequisites that need to be in place before enabling automatic backups for the database system are:

A) Access to the OCI Object Storage service: Automatic backups are stored in the OCI Object Storage service, so you need access to this service in order to enable automatic backups.

C) VCN configured with VPN for secure access to the Oracle Cloud Infrastructure (OCI) Object Storage service: To ensure secure access to the OCI Object Storage service, a Virtual Cloud Network (VCN) needs to be configured with a VPN connection.

B) Private SSH key to the database and D) Connectivity to Swift endpoints are not mentioned as prerequisites for enabling automatic backups.