Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop — Lesson 4: Observability, Security Scanning, Incident Response, and DevOps Governance

Learning Objectives

• Explain the purpose and operating context of Logging, Monitoring, APM, alarms, events, and deployment markers.
• Apply code, dependency, container, and configuration security checks and failed builds, partial deployments, drift, and production incident workflow in a controlled environment.
• Validate outcomes and troubleshoot risks involving DORA-style metrics, audit records, cost, ownership, and improvement backlog.

Detailed Topics

• Logging, Monitoring, APM, alarms, events, and deployment markers
• code, dependency, container, and configuration security checks
• failed builds, partial deployments, drift, and production incident workflow
• DORA-style metrics, audit records, cost, ownership, and improvement backlog

Instructor Demonstration

Demonstrate Logging, Monitoring, APM, alarms, events, and deployment markers for a regulated application delivered from commit to production with auditable OCI DevOps controls; capture the exact configuration, code, command, transaction, query, dashboard, model, schedule, or report evidence that proves the expected result.

Hands-On Exercise

Complete a controlled Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop exercise covering code, dependency, container, and configuration security checks and failed builds, partial deployments, drift, and production incident workflow; introduce an exception involving DORA-style metrics, audit records, cost, ownership, and improvement backlog, diagnose it from evidence, apply the smallest reversible correction, and rerun acceptance checks.

1. Confirm scope, prerequisites, identities, dependencies, data, risks, and expected outcome.
2. Perform the course-specific configuration, development, administration, analysis, or business-process workflow.
3. Capture commands, settings, records, logs, screenshots, reports, metrics, or test results.
4. Compare the observed result with acceptance criteria and document corrective or preventive action.

Scenario Analysis

• Identify the technical or business decision and the stakeholders affected by it.
• Compare security, performance, reliability, compliance, cost, usability, and support trade-offs.
• Define rollback, recovery, communication, evidence, ownership, and escalation requirements.

Troubleshooting Guidance

Diagnose issues involving Logging, Monitoring, APM, alarms, events, and deployment markers, code, dependency, container, and configuration security checks, failed builds, partial deployments, drift, and production incident workflow, DORA-style metrics, audit records, cost, ownership, and improvement backlog without making an unverified production change. Separate symptoms from causes, gather time-correlated evidence, test a reversible hypothesis, validate the correction, and record recurrence controls.

Validation Checklist

• The requirement, environment, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by product-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, support actions, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply Observability, Security Scanning, Incident Response, and DevOps Governance in a realistic Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop scenario and defend the result with documented evidence.