1Z0-1072-26 OCI Architect Associate Course Notes

VCN design centers on subnets, CIDRs, and gateways aligned with traffic needs. Select gateways based on traffic direction (inbound/outbound). Secure VCNs use security lists and NSGs to control network traffic. Subnets, gateways, and security controls work together for reachability. DRGs connect networks via attachments. Route tables, distributions, and policies control transit. Select DRG based on network topology. VPN for secure, encrypted connections. FastConnect for direct Internet access. Design load balancing using OCI Load Balancer or Network Load Balancer based on traffic needs. Consider public/private placement, protocol, source IP, and TLS termination. Troubleshooting VCN reachability involves subnet routing, gateway selection, and security control validation.

• Confusing NAT and Internet gateways – understand their distinct roles.

• Focus on the destination and directionality of traffic when selecting gateways.

Design IAM boundaries using compartments and IAM policies. IAM policies enforce least privilege using subject-verb-resource-location-conditions. Structure compartments for resource organization and policy scope. Use dynamic groups and resource principals for granular authorization. Policy placement controls administrative scope. Authorize workloads with dynamic groups and resource principals. IAM policies control access based on subject, verb, resource, and location. Apply IAM policies with compartment scope for granular access control.

• Confusing IAM policies with identity-domain administrator roles.

• Focus on the scope of the policy – compartment or tenancy.

Select compute based on workload needs. Placement impacts availability and redundancy. Configure Compute instances: Images, boot volumes, and instance types. Design instance pools and configure autoscaling for dynamic scaling. Distribute workloads across fault and availability domains for high availability. Domain placement is independent of other design choices. Select OCI Compute, container instances, or Functions based on application needs. Secure OCI Compute requires independent design of placement, security, and lifecycle operations.

• Confusing fault-domain and availability-domain placement.

• Shapes determine resource allocation. Placement determines availability.

Block Volume design hinges on attachment type, performance, and availability domain constraints. Design Object Storage tiers based on data access patterns. Use lifecycle policies for automated tier transitions and retention. Design File Storage using Block Volumes or Object Storage based on instance needs and data access patterns. Select storage based on access patterns and retention needs. Protect Block Volumes and Object Storage with appropriate access controls and lifecycle policies.

• Assuming Block Volumes are directly tied to instances – they are independent.

• Focus on the interplay between performance, availability, and backup requirements.

Select database services based on engine compatibility, workload, and operational needs. Data Guard provides DR via synchronized standby databases. Protection mode dictates DR strategy. Plan backups, recovery, and migration using OCI databases, prioritizing Data Guard for disaster recovery. Database security: engine choice impacts encryption/isolation. Data Guard: disaster recovery aligned with recovery objectives. Match database services to workload needs considering engine compatibility, administration, scaling, and security.

• Assuming a single database service can handle all workloads.

• Focus on the core requirements – engine, workload, and operational needs.

Design observability using metrics, alarms, logs, events, and notifications. Automate infrastructure with Resource Manager and Terraform. Use tags for infrastructure organization. Set quotas to control resource limits. Configure alarms for proactive monitoring. Manage OCI costs with metrics, alarms, and Resource Manager. Diagnose service health using OCI Monitoring's metrics, alarms, and logs. Configure alarm destinations to ensure appropriate responses.

• Confusing metrics with alarms – they serve different purposes.

• Focus on the intended response to alarms.