1Z0-1085-26 OCI Foundations Associate Course Notes

Design from traffic flow. VCNs are regional; subnets divide address space; route tables choose paths; security lists/NSGs allow traffic; IGW/NAT/Service Gateway/DRG solve different connectivity needs; Load Balancer and DNS solve distribution/name-resolution; VPN, FastConnect, and peering connect networks.

• VCN ≠ subnet: the VCN is the regional network; subnets are address ranges inside it.

• Start with scope: realm → region → VCN → subnet → VNIC/IP.

Choose the execution model from workload needs. Images define software, shapes define compute resources, flexible shapes support right-sizing, instance pools/autoscaling scale horizontally, load balancers distribute traffic, and Registry/Container Instances/OKE/Functions cover cloud-native execution from images to Kubernetes to serverless code.

• Bare metal ≠ automatically faster for every workload; choose it because the requirement needs dedicated physical resources or a supported high-end shape.

• Read the workload clue before the product name.

Know the hierarchy and failure scopes: realm → region → availability domain → fault domain. A tenancy contains compartments; OCIDs identify resources. IaaS/PaaS/SaaS differ by management responsibility, while OCI distributed-cloud options differ by where services run. HA and DR choices follow failure scope, RPO, RTO, and cost.

• Service model answers management responsibility; deployment model answers where/how cloud capability is delivered.

• If the stem asks 'who manages OS/runtime/app?', think service model.

Identity domains organize user populations and authentication settings; groups/dynamic groups identify principals; IAM policies authorize actions by verb/resource/scope. Security is shared. Cloud Guard detects/responds, Security Zones prevent noncompliant changes, Vault/Key Management manages keys, and Secret Management protects credentials.

• Identity domain ≠ compartment: identity domains organize identities/security configuration; compartments organize OCI resources and policy scope.

• Look for 'different MFA/sign-on policies' → identity domain.

Match storage by access semantics: Block Volume = persistent block device, File Storage = shared NFS, Object Storage = object API/buckets with Standard/IA/Archive tiers. Then choose backups, versioning, lifecycle, replication, and volume groups from the required recovery behavior.

• Block Volume ≠ File Storage: Block is a disk device; File Storage is shared NFS.

• If the workload says 'mount as disk / database volume / persistent disk,' think Block Volume.

Translate the desired outcome: tags classify/attribute, tag defaults enforce metadata at creation, quotas restrict compartment allocation, service limits are Oracle-set ceilings, budgets alert on spend, Cost Analysis visualizes cost, reports provide detailed data, Monitoring/Logging/Events/Audit/Notifications handle operational signals.

• Budget = alert; quota = administrator-enforced allocation control; service limit = Oracle-set service constraint.

• Translate the stem's desired outcome before choosing the service.

Database selection is workload- and control-driven. Autonomous AI Database minimizes DBA work and offers workload types such as Transaction Processing/JSON/Lakehouse; Base Database offers more DB-system control and RAC options; Exadata targets Exadata-class Oracle workloads; HeatWave is MySQL-focused analytics; NoSQL targets key-value/JSON-style table workloads.

• Autonomous ≠ 'Oracle Database on a VM with a new license'; the service automates core database operations.

• Start with workload: transactional, analytical, JSON, or need-for-control.