Oracle Cloud Infrastructure DevOps Professional (1Z0-1109-26) - Practice Exam 1

1. A blue-green traffic switch succeeds, but long-running sessions still use the old environment. What should the rollout plan account for?
2. A build downloads dependencies from a private endpoint and times out. Which investigation is appropriate?
3. A build needs dependency vulnerability assessment before promotion. Which OCI integration should be evaluated?
4. A build passes only when a developer's untracked local file exists. What should change?
5. A build produces a release archive, but the delivery stage cannot locate it. What should be inspected?
6. A build pulls a container base image whose tag has changed. Which TWO controls improve reproducibility? Select TWO.
7. A build requires a secret from OCI Vault. Which build specification feature should be evaluated instead of plaintext source variables?
8. A build's tests pass but its secret accidentally appears in logs. What should happen?
9. A compromised build runner may have published a malicious artifact. What response is appropriate?
10. A deployment fails after the artifact was published. What information should operational logs correlate?
11. A deployment needs an explicit human decision before production promotion. Which stage is appropriate?
12. A deployment pipeline can modify every resource in the tenancy although it deploys one service. What is the best correction?
13. A deployment stage needs custom verification logic beyond built-in controls. Which supported integration can be evaluated?
14. A developer force-pushes a release branch after a successful build. Which value still identifies the original built revision?
15. A later pipeline stage needs a version computed during Managed Build. Which mechanism is relevant?
16. A Managed Build stage cannot find a build specification stored under ci/build_spec.yaml. What should be configured?
17. A manual approval is recorded before the final artifact is rebuilt. What governance gap exists?
18. A manually created resource must become Terraform-managed. What is required?
19. A module exposes a variable for unrestricted public ingress. What should production policy do?
20. A pipeline deploys to multiple regions. What should a progressive rollout assess after the first region?
21. A pipeline logs Terraform state to a public artifact location. Why is this a concern?
22. A pipeline run fails with authorization errors after a policy change. What should be checked?
23. A pipeline should build a specific reviewed revision after a repository event. Which input must be preserved through the run?
24. A production pipeline downloads a dependency from an unpinned URL. What is the principal supply-chain concern?
25. A provider version upgrade changes the Terraform plan. Which practice supports a controlled rollout?
26. A release needs promotion from test to production. Which approach best preserves what was tested?
27. A release secret is rotated. How should the application and pipeline consume its replacement?
28. A Resource Manager stack failed after creating some resources. How should a recovery run proceed?
29. A rolling instance-group deployment must keep most hosts serving traffic. Which setting and prerequisite matter?
30. A service needs validation in a parallel environment before switching production traffic, with quick traffic rollback. Which strategy fits?
31. A team must identify exactly which source revision produced a deployed release. What should its delivery records preserve?
32. A team stores large compiled release packages in its Git history. Which separation is more appropriate?
33. A team wants a release metric that reflects user impact rather than only pipeline duration. What should it include?
34. A team wants to delete old container images. Which retention decision is safest?
35. A team wants to expose a release to a limited audience before expanding its impact. Which strategy fits?
36. A team wants to reuse networking infrastructure definitions across environments. Which approach is appropriate?
37. A Terraform plan proposes destroying a production database during an ordinary application update. What should happen?
38. A unit-test command exits nonzero, but later commands allow the build to appear successful. What should be reviewed?
39. After a failed release, what review best supports better delivery reliability?
40. An artifact has the expected version label but fails its recorded checksum. What should the pipeline do?
41. An automatic rollback restores the application version but errors continue. What should be investigated?
42. An emergency manual infrastructure fix was applied during an outage. What should follow?
43. An external repository should trigger a build on approved changes. What must be configured beyond the repository URL?
44. An OKE deployment succeeds technically, but the canary error rate exceeds the release threshold. What should the pipeline do?
45. Blue and green environments use a shared database. Why can a traffic-only rollback still fail?
46. Infrastructure changes require production authorization separate from development. Which boundary is most effective?
47. Multiple pipelines share one Terraform state file without coordination. What risk does this create?
48. Two builds push different images using the same latest tag. What best prevents deployment ambiguity?
49. Which database change best supports a release where old and new application versions temporarily overlap?
50. Which TWO controls strengthen a protected release branch? Select TWO.

Comments — 0