Which of the following TWO statements are TRUE about deleting a Kubernetes cluster? (Choose two.)
Correct Answer: B,C
The correct statements about deleting a Kubernetes cluster are: If you change the auto-generated name of a worker node and then delete the cluster, the renamed worker node is not deleted. Changing the name of a worker node does not affect its deletion when the cluster is deleted. The cluster deletion process does not consider the renamed worker nodes and will delete all worker nodes associated with the cluster. Upon deleting a cluster, no other resources created during the cluster creation process or associated with the cluster (such as VCNs, Internet Gateways, NAT Gateways, Route Tables, Security Lists, Load Balancers, and Block Volumes) are deleted automatically. These additional resources are not automatically deleted when the cluster is deleted. You need to manage the deletion of these resources separately, if desired. Therefore, the correct statements are that the renamed worker nodes are not deleted when the cluster is deleted, and other associated resources are not automatically deleted when the cluster is deleted.
Question 57
Which key pillar of cloud native development should be utilized when a development team needs to automate build, test, and release cycles to achieve rapid and reliable software delivery?
Correct Answer: B
DevOps principles directly address automation across the software delivery lifecycle. Oracle describes DevOps as collaboration between development and operations teams aimed at continuous delivery, with automation applied throughout planning, coding, building, testing, releasing, deploying, operating, and monitoring. OCI specifically identifies CI/CD tooling for automating build, test, release, and deployment activities. Containerization provides consistent application packaging, microservices define an architectural decomposition model, and serverless computing removes much of the underlying infrastructure-management responsibility. None of those technologies by itself defines the automated delivery lifecycle requested in the question. Continuous Integration and Continuous Delivery are core DevOps practices that make software changes repeatable, testable, and deployable at high frequency while reducing manual intervention and release risk. Therefore, the correct cloud-native pillar is DevOps Principles.
Question 58
Which statement is NOT valid regarding pulling and pushing container images in Oracle Cloud Infrastructure Registry (OCIR)?
Correct Answer: C
Statement C is invalid. Oracle states that creating a repository before pushing is the normal workflow. Automatic repository creation occurs only when the tenancy settingCreate repository on first push in root compartmentis enabled and the user has appropriate permissions. Even then, the new private repository is created in the tenancy ' sroot compartment, not a user ' s "home compartment." Oracle Container Registry is OCI-compliant and supports standard Docker commands. Public repositories can be pulled by anyone with internet access and the appropriate image URL without authenticating first. For pushing, Docker images are tagged using a registry path containing the regional registry domain, tenancy namespace, repository name, and version. The tenancy namespace is the automatically generated namespace associated with Object Storage. Therefore, C misstates both the default behavior and repository location.
Question 59
You have created a repository in Oracle Cloud Infrastructure Registry (OCIR) in the us-ashburn-1 (iad) region in your tenancy with the heyoci namespace. Which three are valid tags for an image named myapp? (Choose three.)
Correct Answer: A,C,F
(OPT) iad.ocir.io/myproject/heyoci/myapp:latest The three valid tags for an image named myapp in the heyoci namespace of the Oracle Cloud Infrastructure Registry (OCIR) in the us-ashburn-1 (iad) region are: iad.ccir.io/heyoci/myapp:latest This tag specifies the latest version of the myapp image in the heyoci namespace in the iad region. iad.ocir.io/heyoci/myapp:0.0.2-beta This tag specifies version 0.0.2-beta of the myapp image in the heyoci namespace in the iad region. us-ashburn-1.ocir.io/heyoci/myapp:0.0.2-beta This tag specifies version 0.0.2-beta of the myapp image in the heyoci namespace in the us-ashburn-1 region. The other options mentioned are not valid tags for the given scenario: us-ashburn-1.ocir.io/heyoci/myapp:0.0.2- beta (incorrect format, missing the namespace) iad.ocir.io/myproject/heyoci/myapp:latest (incorrect format, incorrect order of namespace and project) us-ashburn-1.ocir.io/myproject/heyoci/myapp:latest (incorrect format, incorrect order of namespace and project) The correct format for tagging an image in OCIR is < region > .ocir.io/ < namespace > / < repository > : < tag > .
Question 60
Which configuration parser type is mandatory when setting up a custom log with the OCI Unified Monitoring Agent if no log structure parsing is required?
Correct Answer: C
Oracle explicitly states that theNONEparser type is required when configuring the Unified Monitoring Agent even when no particular parsing of the incoming log structure is desired. The agent configuration still requires a parser declaration so it knows how the input should be handled. NONE allows the log content to be collected without applying structural parsing such as JSON, SYSLOG, regular-expression, or Apache-style parsing. Oracle ' s SDK model also lists NONE as a supported parserType value. RAW, DEFAULT, and UNSTRUCTURED are not the documented parser-type identifiers for this purpose. Consequently, administrators configuring custom logs that should be ingested without parsing must explicitly select or specify NONE, making C the correct answer.