Interval is the field that provides the time window for aggregating metric data points plotted on the metric chart. Interval is a parameter that specifies how often metric data points are collected and aggregated by the Monitoring service. For example, an interval of 5 minutes means that metric data points are aggregated every 5 minutes and displayed on the chart. The other options are not fields that provide the time window for aggregating metric data points, but rather other parameters that define the metric query. References: [Interval]

SSH traffic is not allowed in the security list nor on the NSG from the Internet is the correct answer. This is because the security list only allows ingress traffic from 10.0.0.24 on port 22, and the NSG only allows ingress traffic from 10.0.0.0/16 on port 22. Neither of them allows ingress traffic from 0.0.0.0/0 (the Internet) on port 22, which is required for SSH access. The other options are not correct, as they do not explain why SSH access is not possible. References: [Security Lists], [Network Security Groups]

Auth Tokens is the authentication option that you should use to ensure that your custom application with third-party APIs can communicate with OCI resources. Auth Tokens are tokens that can be used as an alternative to passwords when making API calls to OCI services. Auth Tokens can be generated and revoked by users in the OCI Console or CLI, and can be used with any API client that supports basic authentication. The other options are not suitable for this scenario, as they either require OCI’s signature-based authentication or are not applicable for API calls. References: [Auth Tokens]

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]

Live Migration Agent is not a valid Oracle Cloud Agent plugin name. Oracle Cloud Agent plugins are the following1:

• Bastion: Allows secure shell (SSH) connections to an instance without public IP addresses using the Bastion service.
• Block Volume Management: Configures Block Volume sessions for the instance.
• Compute Instance Monitoring: Emits metrics about the instance’s health, capacity, and performance. These metrics are consumed by the Monitoring service.
• Compute Instance Run Command: Runs scripts within the instance to remotely configure, manage, and troubleshoot the instance.
• Custom Logs Monitoring: Ingests custom logs into the Logging service.
• Management Agent: Collects data from resources such as OSs, applications, and infrastructure resources for Oracle Cloud Infrastructure services that are integrated with Management Agent.
• OS Management Service Agent: Enables you to manage updates and patches for the operating system running on your instance.

Live Migration is a feature of Oracle Cloud Infrastructure that enables you to migrate a running instance from one physical host to another without rebooting the instance or impacting its availability. Live Migration does not require any Oracle Cloud Agent plugin to function.

OS Management service is the OCI service that will allow you to complete this task. OS Management service is a service that helps users automate patching and package management for Oracle Linux and Windows instances in OCI. It can also help users monitor and manage system configuration and compliance across their instances. The other options are not suitable for this task, as they do not provide the functionality of OS Management service. References: [OS Management Service]

 Generating Auth Tokens to enable instances in the dynamic group to authenticate with APIs is not a necessary step to complete this set up. This is because Auth Tokens are used to authenticate users, not instances, when making API calls to OCI services. Instance principals are a feature that allows instances to authenticate themselves using certificates, without requiring user credentials or Auth Tokens. The other options are necessary steps to complete this set up, as they enable instances in the dynamic group to make API calls against services using instance principals and IAM policies. References: [Instance Principals], [Auth Tokens]

Premium is the IAM Identity Domain type that you should create if you want a full-featured IDaaS solution that helps you manage workforce authentication and access to all of your Oracle and non-Oracle applications. Premium Identity Domain provides users with access to Oracle Identity Cloud Service, which is an IDaaS solution that offers identity management, single sign-on, multifactor authentication, identity governance, and integration with third-party applications. The other options are not IAM Identity Domain types that provide a full-featured IDaaS solution. References: [Identity Domains], [Oracle Identity Cloud Service]

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.

File systems use Oracle-managed keys by default. Customer can encrypt data in their file system using their own Vault encryption key. The explanation is that File Storage Service encrypts all data at rest using AES-256 encryption algorithm. By default, File Storage Service uses Oracle-managed keys to encrypt and decrypt data. However, you can also use your own Vault encryption key to encrypt data in your file system. To do so, you need to create a key in Vault and associate it with your file system when you create or update it.

Internet Gateway, NAT Gateway, and Service Gateway are three gateways that are created automatically when creating a VCN with the VCN wizard. An Internet Gateway allows public traffic between the VCN and the internet. A NAT Gateway allows private traffic from the VCN to access the internet without exposing the VCN resources to incoming internet connections. A Service Gateway allows private traffic from the VCN to access OCI services such as Object Storage, Email Delivery, and Notifications. The other options are not created automatically by the VCN wizard, but can be added manually later if needed. References: [VCN Wizard], [Gateways]

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.