Free 1Z0-1064-26 sample questions

Correct answer: Task: Manage Service Request Outcomes and Resolutions; Lookup Type: ORA_SVC_SR_RESOLUTION_CD

In Oracle Fusion Service, the task 'Manage Service Request Outcomes and Resolutions' in Setup and Maintenance allows administrators to manage both outcomes and resolutions, as well as the mappings between them. Service request resolutions are stored under the standard lookup type ORA_SVC_SR_RESOLUTION_CD. The other lookup types mentioned (SVC_SR_RESOLUTION_TYPE, ORA_SVC_CLOSURE_REASON, and SVC_SR_STATUS_RESOLUTION) are incorrect or do not represent the seeded resolution lookup.

Correct answer: True

This statement is true. Oracle explicitly recommends prefixing custom outcome codes with 'SVC_' to prevent collisions with seeded lookup codes. Furthermore, when resolutions are mapped to outcomes in the 'Map Resolutions to Outcomes' configuration interface, selecting an outcome in the runtime Resolve Service Request dialog dynamically filters the resolution choice list to display only those mapped entries.

Correct answer: The resolutions were created without being mapped to outcomes; the administrator must navigate to 'Manage Service Request Outcomes and Resolutions' and transfer the resolutions into 'Selected Resolutions' for each relevant outcome.

Creating resolutions using only the task 'Manage Service Request Resolutions' defines the lookup codes under ORA_SVC_SR_RESOLUTION_CD but leaves them unassociated with any outcome. In Fusion Service, the Resolve Service Request dialog filters resolutions based on the selected outcome. If a resolution is not mapped to an outcome via the 'Map Resolutions to Outcomes' section in 'Manage Service Request Outcomes and Resolutions', the choice list remains empty upon selecting that outcome. There is no scheduled process named 'Flatten Service Request Outcomes and Resolutions', and resolution mapping does not require profile option activation or Groovy validation.

Correct answers: Enhancement Logged; No Fault Found

In Oracle Fusion Service out-of-the-box configuration, the seeded outcome 'Unable to Solve Defect Logged' is mapped to: 'Enhancement Logged', 'Training Required', and 'No Fault Found'. Conversely, 'Knowledge Article' and 'Workaround identified' are mapped to 'Solution Provided', while 'Resolved by Customer' is mapped to 'Customer Abandoned'.

'No Fault Found' is one of the ready-to-use resolutions mapped to 'Unable to Solve Defect Logged'.

Correct answer: The isAttributeChanged() function is valid only in 'Before Insert to Database' or 'Before Update to Database' triggers, because changes have already been committed in an After Changes Posted event.

In Application Composer Groovy scripting, isAttributeChanged() checks whether an attribute's in-memory value differs from its original database value. This function operates exclusively within Before triggers (Before Insert or Before Update). Once execution reaches 'After Changes Posted to Database', the entity's current state matches the posted database state, causing isAttributeChanged() to return false or produce an error. Oracle recommends tracking changed values in a Before trigger or using an Object Workflow rule condition instead.

Correct answer: The email template body or subject line is missing the required tracking token, such as {##SrNumber##} or {##MessageId##}.

Oracle Fusion Service's inbound email processor relies on tracking tokens—specifically {##SrNumber##} or {##MessageId##}—embedded in the subject line or message body of outbound emails. When a customer replies, the inbound processor scans for these tokens to associate the incoming message with the existing SR. If the outbound Object Workflow email template omits these tags, the processor cannot correlate the email to the existing record and defaults to creating a new Service Request.