Oracle Utilities 1Z0-1090-24: Work Management & Scheduling

Topic snapshot

Sample questions

These questions are original IT Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.

Question 1

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

Which statement best distinguishes work request intake from later work management steps in Oracle Utilities Work and Asset Cloud Service?

Options:

• A. A work request captures the reported need and can lead to one or more work activities.

• B. A work request is the record used to assign crews and maintain scheduling windows.

• C. A work request is the approval transaction that authorizes work execution and cost posting.

• D. A work request is where technicians record actual labor, materials, and completion results.

Best answer: A

Explanation: In Work and Asset Cloud Service, a work request belongs to the intake part of the process: it captures the reported issue, service need, or initial request for work. It is not the main record for detailed planning, crew scheduling, field execution, or final completion reporting. Those downstream activities are handled through work activities and related lifecycle processes. Approval behavior may exist in the overall process, but the approval transaction is still distinct from the intake record itself. The key distinction is that a work request starts the work-management flow, while work activities carry the operational details needed to plan, schedule, perform, and close the work.

• Scheduling confusion fails because crew assignment and scheduling windows are part of work activity planning and scheduling, not initial intake.
• Execution record mix-up fails because actual labor, material usage, and completion details are captured during execution and closure, not on the intake request.
• Approval overlap fails because approvals may govern parts of the process, but the approval transaction is not the same thing as the work request.

Question 2

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility has a corrective maintenance work activity for a failed recloser. The crew has finished the replacement, entered actual labor and material usage, and submitted completion notes. The supervisor confirms the field work is done and no additional field tasks remain. Finance has not reviewed the captured costs yet, and the team still plans to verify the asset service history update. What is the best next step?

Options:

• A. Administratively close the work activity

• B. Validate the asset service history entry

• C. Perform cost review for the completed charges

• D. Record business completion for the work activity

Best answer: D

Explanation: Business completion marks the point at which the field work itself is finished. In this scenario, the crew has completed the repair, entered actuals, and the supervisor has confirmed that no more operational work is needed, so the next lifecycle step is to record business completion. Administrative closure is a later control step that typically follows follow-up activities such as cost review, exception handling, and confirmation that related records updated correctly. Cost review and service history validation are important safeguards, but they do not replace the status change that recognizes the work is operationally done. Complete the work first; close it only after downstream validation is satisfied.

• Premature closure fails because administrative closure should follow business completion and post-work checks, not replace them.
• Cost review first is out of sequence because reviewing charges is a downstream control after the work is marked complete.
• History validation first is also later in the process because checking service history accuracy is a follow-up verification step.

Question 3

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility is reviewing how to manage a planned field job in Oracle Utilities Work and Asset Cloud Service.

Exhibit:

Job request summary
Reason: extend service to a new subdivision
Existing asset failure: none reported
Scope: install 12 poles, 1 transformer, and new conductor
Planned phases: design, permitting, material staging, field build, closeout
Expected duration: 4 weeks

Based on the exhibit, what is the best supported action?

Options:

• A. Create an ordinary corrective work activity

• B. Manage the job through construction-work processes

• C. Delay work creation until service history shows a failure

• D. Treat the job as preventive maintenance

Best answer: B

Explanation: Construction work is the right fit when the job is a planned build or expansion effort, especially when it creates new assets and includes project-style phases such as design, permitting, staging, build, and closeout. In the exhibit, no existing asset has failed, so there is no corrective maintenance trigger. The scope is also broader than a routine repair because it installs new poles, a transformer, and conductor over multiple weeks. Preventive maintenance is also not appropriate because the work is not recurring upkeep on an existing asset. The key distinction is that this request is for new infrastructure delivery, not restoration of an asset already in service.

• Corrective misread fails because the exhibit shows no failed asset that needs repair.
• PM confusion fails because preventive maintenance is scheduled upkeep, not a one-time network expansion.
• Wait for failure fails because construction work should be planned from the current request, not triggered by later service-history evidence.

Question 4

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility’s maintenance team receives many work requests with only free-text descriptions. Dispatchers often cannot identify the affected asset quickly, service history is split across unrelated records, schedulers cannot group similar work well, and reports are inconsistent. The implementation team wants a configuration change that improves data quality at the earliest point in the process. Which decision best supports this requirement?

Options:

• A. Add an extra approval step before a work request can create a work activity

• B. Define more detailed crew calendars and scheduling windows for each service area

• C. Require asset or location reference and standardized issue codes during work request intake

• D. Make failure cause and repair action mandatory when the work activity is completed

Best answer: C

Explanation: The best implementation choice is to improve data quality at work request intake, not later in the lifecycle. When requestors must identify the relevant asset or location and select standardized issue codes, planners and dispatchers can assess the problem faster, service history can be tied to the correct record, schedulers can group and prioritize similar work more accurately, and reporting uses consistent categories instead of unreliable free text.

If poor data enters at intake, downstream processes usually inherit that weakness. Completion details, approvals, and scheduling rules may help later operational steps, but they do not reliably correct missing or inconsistent intake information. The key takeaway is that structured intake data is the foundation for better maintenance response and cleaner operational history.

• Late lifecycle fix making completion details mandatory improves closeout quality, but it does not help initial triage or early scheduling.
• Approval control adding approvals changes governance, not the quality or structure of intake data.
• Scheduling scope refining crew calendars helps assignment after planning, but it cannot repair missing asset identification or inconsistent request categorization.

Question 5

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility is configuring a quarterly inspection preventive maintenance program. Every asset built from asset specification POLE_SWITCH_STD should generate one work activity every 90 days. In testing, some pole switches receive two generated work activities because an older asset-level PM is still active, and a few non-switch assets are included. Which configuration decision best supports the requirement?

Options:

• A. Use work activity type to define applicability and keep both PMs active.

• B. Use approval setup to stop duplicate work after generation.

• C. Use one active PM on POLE_SWITCH_STD and deactivate overlapping asset PMs.

• D. Use crew scheduling windows to prevent two visits per cycle.

Best answer: C

Explanation: Preventive maintenance should be configured at the scope that matches the intended asset population. When all qualifying assets share the same asset specification, the cleanest setup is one active PM program tied to that specification. That keeps applicability aligned to the correct assets and avoids unintentionally including other asset types. Duplicate generated work commonly occurs when overlapping PM definitions are active at different scopes, such as both asset-specification and individual-asset PMs covering the same cycle. Approval rules, status handling, and crew scheduling occur after PM generation, so they do not correct bad applicability or prevent the extra work from being created. The key is to define one generating PM at the right asset scope and remove competing PM definitions.

• Wrong scope using work activity type targets the generated work record, not which assets qualify for the PM.
• Too late in lifecycle approval setup acts after generation, so duplicate or mis-scoped work can already exist.
• Scheduling is downstream crew windows can reduce assignment conflicts, but they do not control PM applicability or generation logic.

Question 6

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

During preventive maintenance testing, a team runs the generation process for a pump asset. Which validation step best confirms that the PM program created the intended maintenance work?

Options:

• A. Create a work request for the pump and verify that it can be approved.

• B. Review service history to confirm that previous maintenance was completed.

• C. Check the asset specification to confirm the pump’s standard characteristics.

• D. Review the generated work activity for the pump and verify its planned date and task details.

Best answer: D

Explanation: In Work and Asset Cloud, preventive maintenance setup is ultimately validated by the work it generates. The most direct validation step is to review the resulting work activity and confirm it was created for the correct asset, with the expected planned timing and maintenance details. That shows the PM program produced actionable maintenance work as intended.

Asset specification data helps define standard asset information, but it does not prove that PM generation created a new maintenance record. Service history reflects past or completed work, so it is not the primary place to validate newly generated PM work. A work request is an intake record and is different from system-generated preventive maintenance execution.

The key check is the generated work activity, not a related master or history record.

• Asset definition only checking the asset specification verifies reference data, not whether PM generation produced a maintenance record.
• Past work focus reviewing service history looks backward at completed or recorded work rather than newly generated planned work.
• Wrong transaction type creating a work request tests intake and approval flow, not preventive maintenance generation output.

Question 7

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility uses Work and Asset Cloud to schedule field work. A planner narrows a linked work activity’s scheduling window from 10:00-14:00 to 07:00-09:00 to satisfy a customer request. The activity requires a switching-certified crew and a bucket truck. The only qualified crew starts at 08:00, and the bucket truck is reserved until 09:30. If the planner changes the window without validating the linked work activity and resource constraints, what is the most likely consequence?

Options:

• A. The work request will be regenerated as preventive maintenance for the new window.

• B. The activity may remain unscheduled because qualified resources are unavailable in the new window.

• C. The asset service history will move to the new time before the work starts.

• D. The customer window will be honored because scheduling automatically bypasses resource constraints.

Best answer: B

Explanation: In Work and Asset Cloud, a scheduling window is only one part of the scheduling decision. The linked work activity must still match required crew qualifications, shift availability, and equipment availability. Here, the new 07:00-09:00 window conflicts with both the qualified crew start time and the bucket truck reservation, so the change creates an infeasible scheduling situation. The likely result is a failed scheduling attempt, an unscheduled activity, or a missed appointment expectation—not an automatic override of resource rules. The key implementation practice is to validate the new window against linked labor and equipment constraints before committing the change.

• Auto-override assumption fails because scheduling windows do not cancel qualification, shift, or equipment requirements.
• History confusion fails because service history reflects executed work, not a planning-time window update.
• Wrong record type fails because changing a work activity window does not regenerate the work as preventive maintenance.

Question 8

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

During UAT, a utility tests a job to replace an overhead line segment, install 12 new poles, and add a new transformer. The implementation team created separate ordinary corrective work activities from a service call. Supervisors report they cannot manage the effort as one build job, see rolled-up job costs, or track the new assets within a construction package. What is the most likely cause?

Options:

• A. The approval workflow is missing a project-cost review step.

• B. The job was created as corrective work instead of construction work.

• C. The scheduler is missing a crew-calendar setup for linked tasks.

• D. The new asset specifications are incomplete for pole installation.

Best answer: B

Explanation: Construction work is used when the organization needs to manage a coordinated build, replacement, or installation effort as a single construction package, often with multiple related activities, new asset creation, and rolled-up job visibility. Ordinary corrective work is meant for routine repair or correction of existing assets. In this scenario, the key symptoms are not just scheduling or approval problems; the team lacks the construction-level grouping and cost view expected for a capital-style build job. The best first fix is to manage the effort through construction-work processes so the work is organized in the right business context. Scheduling or approvals can support that process, but they do not replace it.

• Scheduling setup affects crew assignment and timing, but it does not turn routine corrective work into a construction package.
• Approval workflow can control review and authorization, but missing approvals alone would not explain the lack of construction-level grouping.
• Asset specifications matter for master data quality, but incomplete specifications do not by themselves cause a build job to be managed in the wrong process.

Question 9

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

Which statement best distinguishes a work request from a work activity in Oracle Utilities Work and Asset Cloud?

Options:

• A. A work request records the need for work, while a work activity holds task planning, resource planning, and completion details.

• B. Task plans, resource assignments, and completion results belong on the asset record rather than on work activities.

• C. A work request stores planned labor and actual completion data, while a work activity only documents the reported issue.

• D. A work activity is mainly an approval container, while a work request is the primary crew execution record.

Best answer: A

Explanation: In Work and Asset Cloud, a work request represents the initial demand for work such as a reported problem, service need, or request for action. A work activity is the operational record used to organize and control execution. That is where implementation teams expect to manage planning and lifecycle details such as tasks, resources, status progression, and completion information. Asset records provide context about the equipment or location, but they are not the main transaction for planning and closing the job. A good implementation distinction is: request = identify the need; activity = plan, perform, and complete the work.

• Planning on the request is incorrect because planned labor, resources, and completion details are part of the execution record, not the intake record.
• Approval-only activity is incorrect because approvals may apply in the process, but the work activity is broader and manages work execution.
• Asset as execution record is incorrect because the asset provides master context and history linkage, not the primary transaction for task and resource planning.

Question 10

Topic: Work Management, Preventive Maintenance, Construction Work, and Scheduling

A utility is validating construction work setup during system testing. Planners can save a construction work record, but nothing appears in Scheduling for the job and no related work activities are listed.

Exhibit:

What is the most likely cause, or best first fix?

Options:

• A. Move the construction work into an approved, plannable status

• B. Rebuild the asset hierarchy for the job location

• C. Extend the crew scheduling window for the organization

• D. Add missing storeroom balances for project materials

Best answer: A

Explanation: In construction work management, Scheduling works with actual work activities, not just the parent construction work record. The exhibit shows the organization’s scheduling setup is already active, but the construction work is still in Draft with approval still Pending and has zero related work activities. That points first to lifecycle/state control, not to a scheduling configuration problem. During implementation, the best first validation is to confirm the construction work has progressed to the status that allows related work activities to be created and planned.

The closest distractor is the scheduling-window change, but that only affects visibility or assignment of activities that already exist.

• Asset context issue rebuilding the asset hierarchy may improve location or relationship accuracy, but it does not explain zero related work activities on a draft construction work record.
• Material availability issue storeroom balances affect whether materials can be issued, not whether initial construction work activities become available for planning.
• Scheduler visibility issue extending the scheduling window matters only after plannable work activities exist for the scheduler to place.

Continue with full practice

Use the Oracle Utilities 1Z0-1090-24 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try Oracle Utilities 1Z0-1090-24 on Web View Oracle Utilities 1Z0-1090-24 Practice Test

Related focused pages

• Free Oracle Utilities 1Z0-1090-24 Full-Length Practice Exam
• Scope and User Experience
• Assets and Locations
• Inventory and Service History
• Approvals and Auditability
• Administration and Configuration
• Integrations and Operations

Free review resource

Read the Oracle Utilities 1Z0-1090-24 Cheat Sheet for compact concept review before returning to timed practice.