PDF 1z0-1085-23 Study Guide

Oracle Cloud Infrastructure File Storage service provides a durable, scalable, secure, enterprise-grade network file system. You can connect to a File Storage service file system from any bare metal, virtual machine, or container instance in your Virtual Cloud Network (VCN).

You can control the access of the file system from FSS by applying some security rules and others but the services it self not related to security but it related to shared storage

A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. In addition, the physical hardware in a fault domain has independent and redundant power supplies, which prevents a failure in the power supply hardware within one fault domain from affecting other fault domains.

To control the placement of your compute instances, bare metal DB system instances, or virtual machine DB system instances, you can optionally specify the fault domain for a new instance or instance pool at launch time. If you don't specify the fault domain, the system selects one for you. Oracle Cloud Infrastructure makes a best-effort anti-affinity placement across different fault domains, while optimizing for available capacity in the availability domain. To change the fault domain for an instance, terminate it and launch a new instance in the preferred fault domain.

Use fault domains to do the following things:

Protect against unexpected hardware failures or power supply failures.

Protect against planned outages because of Compute hardware maintenance.

Visual Logs is not a valid log type supported by the Oracle Cloud Infrastructure (OCI) Logging service. The Logging service supports three kinds of logs: Audit logs, Service logs, and Custom logs5

• Audit logs are logs related to events emitted by the OCI Audit service, such as API calls or console actions performed by users or services in your tenancy. Audit logs are automatically enabled and available for viewing or searching in the Logging service5
• Service logs are logs emitted by OCI native services, such as API Gateway, Events, Functions, Load Balancer, Object Storage, and VCN Flow Logs. Each of these supported services has predefined logging categories that you can enable or disable on your respective resources. For example, you can enable read and write access events for Object Storage buckets, or ingress and egress traffic for VCN subnets5
• Custom logs are logs that contain diagnostic information from custom applications, other cloud providers, or an on-premises environment. Custom logs can be ingested through the API, or by configuring the Unified Monitoring Agent. For example, you can send logs from Apache web servers, Oracle databases, or Kubernetes clusters to the Logging service for analysis and monitoring5