DO280 and EX280 Practice: Original Tasks With Worked Solutions

Practise OpenShift administration through original tasks tied to the published objectives, with explicit desired results and checks. The tasks here cover resource selection, service routing, scoped access, quotas, network policy and operator review in a supplied training scenario. One offline Python fixture demonstrates an equality-selector mismatch and correction; it does not contact a cluster.

Jan 25, 2025 - 18:06
Updated: 
106.2k

OpenShift in IT Infrastructure · Certification preparation

DO280 and EX280 Practice: Original Tasks With Worked Solutions

Quick answer: Practise OpenShift administration through original tasks tied to the published objectives, with explicit desired results and checks. The tasks here cover resource selection, service routing, scoped access, quotas, network policy and operator review in a supplied training scenario. One offline Python fixture demonstrates an equality-selector mismatch and correction; it does not contact a cluster. Use a properly authorised, version-matched lab for actual OpenShift work. Confirm your designated EX280 version and use current official documentation, keeping these exercises separate from confidential exam content.

Key takeaways

  • Use original tasks and public objectives.
  • Write the desired state before selecting a solution.
  • Check selectors, permissions and network paths separately.
  • Use allowed and denied cases when verifying access.
  • Treat an offline model as a concept check, not cluster validation.

Table of Contents

What environment and scope do these practice tasks assume?

Imagine a training platform with two projects, catalog and warehouse, and supplied identities for each team. The task is to make the catalog application usable by its intended clients while maintaining the agreed separation. Keep all changes in a dedicated lab with permission to perform them.

DO280’s current course page and EX280’s current exam page describe public scope on OpenShift 4.22. The exam page also says multiple versions are in use, so check your designated objectives. These are original learning tasks, not recalled questions. No cluster changes were executed for this article; the displayed local fixture has a narrower, explicitly tested purpose.

Lab detailConfirm before actual platform work
VersionDesignated objectives and matching product documentation
AuthorityPermitted projects, identities and administrator tasks
RecoveryReset or rollback arrangement approved by the lab owner
VerificationExpected results and supplied clients for allowed/denied checks

Task 1: How do you make the application’s labels consistent?

Request: identify the catalog frontend Pods and make the intended Service selector agree with their labels. Start by inspecting the supplied manifest and object relationships. A Pod name and a label are different fields. Kubernetes labels documentation explains how selectors use label requirements.

Worked solution: decide which label set identifies the intended frontend, then keep that set consistent in the relevant workload template and Service selector. Verify the actual resources in the training project after the change, because editing a file alone does not show that a cluster has the intended state. Do not select unrelated warehouse or worker Pods merely to obtain a non-empty result. The next local exercise isolates the equality comparison.

Task 2: Why does the sample Service select no Pod?

Request: explain why app=catalog and tier=web selects nothing from the invented data. Worked solution: the catalog Pod uses tier=frontend. Correct that selector value while retaining app=catalog. Kubernetes Service documentation describes the Service relationship to selected Pods.

Run this checked offline Python fixture to see the comparison. It makes no API calls and modifies only its local in-memory selector.

pods = [
    {"name": "catalog-a", "labels": {"app": "catalog", "tier": "frontend"}},
    {"name": "worker-a", "labels": {"app": "worker", "tier": "backend"}},
]
selector = {"app": "catalog", "tier": "web"}

def selected_names(required):
    return sorted(
        pod["name"] for pod in pods
        if all(pod["labels"].get(key) == value for key, value in required.items())
    )

print("before:", selected_names(selector))
selector["tier"] = "frontend"
print("after:", selected_names(selector))

Expected output is before: [] followed by after: ['catalog-a']. This models simple equality requirements only. It does not validate a Service manifest, readiness, ports, EndpointSlices or actual traffic. In a lab, check those separately before claiming the application is reachable.

Task 3: How do you grant a team access without broad cluster privileges?

Request: give the supplied catalog team the permitted application-management actions in its own project, while excluding warehouse administration. Worked solution: choose the appropriate role and a binding at the intended namespace scope under the lab's policy. Confirm the group membership and the identity used for verification.

The Kubernetes RBAC reference distinguishes roles and binding scopes. Verify an allowed action in catalog and a relevant denied action outside that scope using the supplied test identity. Do not infer success from an administrator's view. Avoid granting cluster-wide administrative rights simply to bypass a failed check; investigate the resource, action, subject and binding scope that the request actually needs.

Task 4: How do you investigate an admission failure involving quota?

Request: a new catalog workload cannot be admitted after a quota is introduced. Worked solution: inspect the actual rejection, current quota usage and the workload's declared requests and limits. Compare the proposed resource consumption with the policy and any defaulting supplied by a LimitRange.

Kubernetes quota documentation explains quota admission behaviour. A quota-related rejection and a scheduling failure are different stages, so use the observed event to choose the next check. Correct the workload or approved policy only within the stated lab request. Then verify the resulting object and intended application behaviour. Increasing every quota without understanding the request would hide the learning problem and could exceed the exercise's scope.

Observed problemWorked investigation direction
No selected PodsCompare actual Pod labels with the Service selector
Permission deniedCheck subject, action, resource and binding scope
Quota rejectionCompare admission message, usage and declared resources
Application unreachableCheck service relationship and the relevant network paths separately

Task 5: How do you check network separation without breaking intended access?

Request: permit the stated catalog-client path while preventing the specified warehouse-to-catalog path. Worked solution: map the required source, destination and ports before choosing selectors. Review existing policies because their combined behaviour matters.

Kubernetes network-policy documentation explains the model and its dependence on supporting networking implementation. In the authorised lab, test the intended allowed path and the denied path with supplied clients. Consider required supporting traffic such as name resolution, and distinguish ingress through the platform's routing components from direct Pod communication. The policy's existence is not a traffic test. Record the actual outcome and investigate an unexpected result instead of weakening all network controls.

Task 6: What should you verify before and after an Operator change?

Request: review a proposed lab Operator installation for the task's allowed scope. Worked solution: use the version-matched OpenShift documentation to check the Operator, installation scope, permissions and dependencies. Confirm the lab owner's approval before making a platform-level change.

After an authorised installation or update, inspect the relevant resource state, events and the intended function. A successful installation record alone does not show that the application requirement is satisfied. Record the rollback or recovery arrangement before the change. Finish the exercise set by writing what was checked, what remains untested and which task needs repetition. Keep actual platform observations separate from the offline selector output and do not treat either as a guarantee of exam readiness.

Related reading: compare DO280 and EX280 training; build command-line foundations.

If you want instructor feedback, ask WebAsha for a syllabus, supervised lab arrangements and written access terms before enrolling.

References

Frequently Asked Questions

They are original learning tasks based on public concepts and objectives, with no confidential questions, recalled exam content or predicted assessment items.

The fixture uses invented local dictionaries and makes no network or cluster calls, so it requires only a suitable Python environment.

It demonstrates a simple equality-selector mismatch and correction for the supplied data, while actual Service behaviour requires separate platform checks.

Selection is one relationship; readiness, ports, endpoint handling and relevant network paths still need appropriate checks in the authorised lab.

A denied-case check helps assess the intended boundary, while an administrator’s successful action does not show the supplied team identity has appropriate scope.

Quota can reject admission before scheduling, so inspect the actual message and resource state to choose the relevant investigation path.

Actual behaviour depends on policy combinations and supported networking implementation, so verify the required allowed and denied paths in the lab.

Check your designated exam version and objectives because the current public page names 4.22 while also noting that multiple versions are in use.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Wow Wow 0
Sad Sad 0
Angry Angry 0
Aayushi Sinha

With a passion for staying on the cutting edge of technology trends, I am dedicated to delivering content that not only informs but also inspires. Whether you need in-depth analysis pieces, informative guides, or thought-provoking opinion pieces, I craft content that resonates with tech enthusiasts and professionals alike.