First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Service Center Overview and Solution Architecture
In an Oracle Service Center 2026 implementation, which component is primarily responsible for storing customer, contact, and installed-asset records that service requests reference?
- The Oracle Fusion customer data model Correct answer.
- The Service Center knowledge base
- The workflow notification engine
- The analytics semantic layer
Explanation
Service Center is built on the Oracle Fusion customer data model, which holds parties, contacts, accounts, and installed assets. Service requests link to these records by reference rather than duplicating the data. Knowledge and analytics components consume this data but do not own the master records.
Question 2Service Center Overview and Solution Architecture
A solution architect is mapping the layers of an Oracle Service Center 2026 deployment. Which layer is responsible for enforcing service-level milestones and escalating breached service requests?
- The user interface layer
- The data storage layer
- The service request processing layer Correct answer.
- The integration layer
Explanation
Service request processing covers the business logic that governs the request lifecycle, including milestone tracking, escalation, and assignment rules. The UI layer only presents data, integration connects external systems, and storage persists records. Milestone enforcement is core processing behavior, not a presentation or connectivity concern.
Question 3Service Center Overview and Solution Architecture
Which Oracle Service Center 2026 capability lets an agent see a unified timeline of a customer's prior service requests, orders, and interactions while working a current request?
- The message template editor
- The customer hub view Correct answer.
- The approval workflow console
- The catalog administration page
Explanation
The customer hub presents a consolidated context including past service requests, transactions, and interactions so agents can resolve issues with full history. Approval consoles manage authorizations, catalog pages configure offerings, and template editors manage outbound text. Only the hub aggregates cross-object customer context.
Question 4Service Center Overview and Solution Architecture
An implementation team must decide where to configure categories that drive routing and reporting for incoming service requests. In Oracle Service Center 2026, which construct serves this purpose?
- The resource organization tree
- The service request category hierarchy Correct answer.
- The product group hierarchy
- The price list structure
Explanation
Service request categories form a hierarchy that classifies issues and drives routing, assignment, and reporting. Product groups organize offerings, resource organizations structure agents, and price lists govern charges. Category is the classification used specifically for request handling.
Question 5Service Center Overview and Solution Architecture
Which Oracle Service Center 2026 feature provides agents with suggested resolutions drawn from previously solved requests and authored articles?
- The billing schedule generator
- The knowledge search and recommendation service Correct answer.
- The territory assignment engine
- The audit trail viewer
Explanation
Knowledge search surfaces relevant articles and prior solutions to agents, and recommendation services suggest resolutions based on request context. Territory assignment routes work to agents, billing schedules generate charges, and audit viewers track changes. Only knowledge services suggest resolutions.
Question 6Service Center Overview and Solution Architecture
A service organization wants external customers to log and track their own service requests without agent assistance. Which Oracle Service Center 2026 channel supports this requirement?
- The agent desktop macro set
- The internal call script library
- The batch data import utility
- The self-service web portal Correct answer.
Explanation
The self-service portal exposes request creation and status tracking directly to customers, reducing agent workload. Call scripts and macros are internal agent aids, and batch import is an administrative data tool. Only the portal provides a customer-facing channel.
Question 7Service Center Overview and Solution Architecture
An architect is designing routing so that high-priority requests for a premium customer segment reach a dedicated team. Which combination of Oracle Service Center 2026 constructs is most appropriate?
- Message templates plus audit policies
- Sandbox sets plus deployment plans
- Price lists plus billing schedules
- Category hierarchy plus territory assignment rules Correct answer.
Explanation
Category classification identifies the type of issue while territory assignment rules evaluate attributes such as priority and customer segment to route work to the right team. Price lists, templates, and sandboxes serve commercial, communication, and lifecycle purposes respectively. Routing requires classification plus assignment logic.
Question 8Service Center Overview and Solution Architecture
A customer reports the same printer failure three times in one month. Which Oracle Service Center 2026 data relationship best supports recognizing that these requests concern the same physical device?
- Attaching a unique price list to each request
- Assigning each request to a different agent
- Creating a separate customer account per request
- Linking each request to the installed asset record Correct answer.
Explanation
Installed asset records represent the specific customer-owned item, so linking requests to the same asset exposes repeat-failure patterns. Reassigning agents, duplicating accounts, or varying price lists obscures rather than reveals the shared device. Asset linkage is the designed mechanism for device-level history.
Question 9Service Center Overview and Solution Architecture
A service manager wants automatic escalation when a request passes its first response milestone without agent action. Which Oracle Service Center 2026 mechanism implements this?
- Milestone configuration with escalation actions on the service request Correct answer.
- A catalog item with a shorter description
- A user role with read-only privileges
- A knowledge article flagged as internal
Explanation
Milestones define time targets and can trigger escalation actions such as reassignment or notification when breached. Catalog descriptions, article flags, and role privileges do not monitor elapsed time. Escalation is achieved through milestone definitions and their associated actions.
Question 10Service Center Overview and Solution Architecture
During design, a team must decide how agents will capture structured diagnostic answers from customers before a request is created. Which Oracle Service Center 2026 capability fits best?
- A free-text note field on the account record
- A dashboard showing historical volumes
- A scheduled batch job that parses emails
- A guided process with dynamic questions attached to the request type Correct answer.
Explanation
Guided processes present structured, conditional questions so agents gather consistent diagnostic data before submission. Free-text notes lack structure, batch parsing is retrospective, and dashboards report rather than collect. Guided intake is the designed mechanism for structured capture.
Question 11Service Center Overview and Solution Architecture
An implementation requires that a request automatically create a follow-up activity for the assigned agent once resolved. Which Oracle Service Center 2026 design element accomplishes this?
- A lifecycle status transition configured with an automated action Correct answer.
- An additional price list assigned to the account
- A new category node added to the hierarchy
- A manual reminder sent by the team lead
Explanation
Lifecycle status transitions can carry automated actions, so moving a request to Resolved can spawn a follow-up activity. Manual reminders are not automatic, category nodes classify, and price lists are commercial. Automation belongs in the configured transition.
Question 12Service Center Overview and Solution Architecture
A company wants customers to check request status through a conversational assistant rather than a web form. Which architectural consideration is most relevant in Oracle Service Center 2026?
- Adding more agents to the premium territory
- Shortening the text of message templates
- Increasing the number of category nodes in the hierarchy
- Exposing service request operations through integration interfaces consumable by the assistant channel Correct answer.
Explanation
A conversational channel requires programmatic access to request operations, so integration interfaces must be exposed and secured for the assistant. Category depth, staffing, and template length affect operations but do not enable a new channel. Channel enablement is fundamentally an integration concern.
Question 13Service Center Overview and Solution Architecture
Two business units share one Oracle Service Center 2026 instance but require different request layouts and mandatory fields. Which design approach best meets this without custom code?
- Store the differences in a knowledge article
- Use page layout and dynamic layout assignment by business unit Correct answer.
- Disable validation for the second business unit
- Create two separate databases for each unit
Explanation
Layout assignment rules can present different page configurations and required fields based on attributes such as business unit. Separate databases duplicate the platform, disabling validation removes control, and articles cannot alter forms. Declarative layout assignment satisfies the requirement.
Question 14Service Center Overview and Solution Architecture
An architect must explain why analytics should not query transactional tables directly during peak hours in Oracle Service Center 2026. Which rationale is most accurate?
- Analytics should read from a dedicated reporting store to avoid contending with transactional workloads Correct answer.
- Analytics queries automatically delete transactional records
- Analytics requires the transactional database to be offline
- Transactional tables cannot be read by reporting users under any configuration
Explanation
Reporting is decoupled from transaction processing so heavy analytical queries do not degrade agent response times. Analytics does not delete records, transactional tables can be read when configured, and the database need not be offline. The separation exists for performance isolation.
Question 15Service Center Overview and Solution Architecture
A global deployment needs agents in three regions to see requests during their local business hours while sharing one queue. Which Oracle Service Center 2026 configuration supports this?
- Removing all assignment rules so requests stay unassigned
- Territory and assignment rules that consider region and time zone attributes Correct answer.
- A single hard-coded assignment to one administrator
- Routing every request to the first available agent regardless of region
Explanation
Assignment rules can evaluate region and time zone so requests reach agents during local hours while the queue remains shared. Hard-coding one administrator creates bottlenecks, removing rules leaves work unassigned, and ignoring region breaks coverage. Attribute-driven assignment is the correct design.
Question 16Service Center Overview and Solution Architecture
A service organization wants to measure first-contact resolution across channels. Which Oracle Service Center 2026 architectural element primarily supplies the underlying metrics?
- The service analytics subject areas built on request and interaction data Correct answer.
- The user role hierarchy
- The catalog item definition
- The message template repository
Explanation
Analytics subject areas model request and interaction facts, enabling measures such as first-contact resolution by channel. Templates, catalog items, and role hierarchies define content, offerings, and access rather than metrics. Measurement depends on the analytical data model.
Question 17Service Center Overview and Solution Architecture
A customer emails a question, and the agent replies with a solution article link that the customer confirms resolves the issue. Which Oracle Service Center 2026 outcome demonstrates the value of the knowledge-request linkage?
- The article is deleted from the knowledge base
- The request is resolved on first contact and the article's usage is recorded Correct answer.
- The customer account is merged with another account
- The request is automatically reassigned to a different territory
Explanation
Linking knowledge to a request records article usage and supports first-contact resolution, feeding effectiveness reporting. Reassignment, deletion, and account merging are unrelated consequences. The linkage's value lies in resolution speed and measurable knowledge effectiveness.
Question 18Service Center Overview and Solution Architecture
An architect is evaluating extensibility for Oracle Service Center 2026 and wants to add a custom field that participates in routing and reporting. Which approach is most aligned with the platform's declarative model?
- Add the value to the agent's personal notes
- Encode the value inside the request description text
- Define the field on the service request object so it is available to rules and analytics Correct answer.
- Store the value only in an external spreadsheet
Explanation
Fields defined on the service request object become first-class attributes usable by assignment rules and reporting subject areas. Spreadsheets, description text, and personal notes are unstructured and invisible to routing and analytics. Declarative extension keeps the attribute governable.
Question 19Service Center Overview and Solution Architecture
A program team must move configuration from a test environment to production while preserving the ability to roll back. Which Oracle Service Center 2026 lifecycle practice best supports this?
- Package changes in a sandbox set and publish through a managed deployment plan with validation Correct answer.
- Ask agents to re-enter configuration manually in production
- Make changes directly in production and document them afterward
- Copy the production database over the test database nightly
Explanation
Sandbox sets capture configuration changes, and deployment plans validate and publish them in a controlled, reversible manner. Direct production edits lack control, database copying moves data rather than configuration, and manual re-entry invites error. Managed deployment provides traceability and rollback.
Question 20Service Center Overview and Solution Architecture
An enterprise wants a single service request to be visible to both a customer-service team and a field-service team, each with different permitted actions. Which Oracle Service Center 2026 design principle governs this?
- Duplicate requests created separately for each team
- A single shared login used by all team members
- Role-based access combined with request sharing across organizations Correct answer.
- Removing all security roles from the request object
Explanation
Role-based access determines which actions each team may perform, while sharing rules make the same request visible across organizations. Duplicating requests fragments history, shared logins destroy accountability, and removing roles eliminates control. The combination of roles and sharing meets the requirement securely.
Question 21Security, Users, Roles, and Data Access
In Oracle Service Center, which construct is used to group users so that permissions can be granted once and inherited by every member?
- A responsibility attached to a user account
- A role assigned to users and granted privileges Correct answer.
- A profile option set at the site level
- A permission group assigned to individual user records
Explanation
Roles are the grouping construct: privileges are granted to the role, and users who are assigned the role inherit those privileges. This keeps administration scalable because access changes are made once on the role rather than per user. Responsibilities and profile options are different mechanisms that control menus and behavior, not reusable privilege bundles.
Question 22Security, Users, Roles, and Data Access
A security administrator wants a new user to see the Service Center menus on first login. Which assignment is required?
- Assign the user to a department
- Subscribe the user to a notification template
- Grant the user the system administrator profile option
- Assign the user a role with the required Service Center privileges, including ViewServiceCenter Correct answer.
Explanation
Service Center uses role-based access. Assign the user an appropriate role that grants the required navigation privileges, including ViewServiceCenter. Department membership and notification subscriptions do not grant this access, and a profile option does not replace the required role and privileges.
Question 23Security, Users, Roles, and Data Access
Which statement best describes the relationship between users, roles, and privileges in Oracle Service Center security?
- Privileges are assigned directly to users and roles are informational only
- Users are assigned to privileges and roles are derived automatically
- Roles are assigned to users and privileges are granted to roles Correct answer.
- Privileges are granted to responsibilities and users inherit them through menus
Explanation
The model is user to role to privilege: users are assigned roles, and privileges are attached to those roles. Authorization checks resolve the union of privileges from all roles a user holds. Assigning privileges directly to users is not the intended pattern because it defeats centralized administration.
Question 24Security, Users, Roles, and Data Access
A user can open the Service Request screen but cannot edit records owned by another team. Which security layer most likely explains this outcome?
- The responsibility does not include the edit menu entry
- The user has too many roles assigned
- The user's role lacks the data privilege or the record is outside the user's data access scope Correct answer.
- The user's profile option for language is set incorrectly
Explanation
Being able to open a screen shows the responsibility grants the menu, so the restriction must come from the data layer. Data access is governed by privileges plus the scope of records a user may touch, such as team or organization boundaries. Language settings and role count do not restrict record editing in this way.
Question 25Security, Users, Roles, and Data Access
Which mechanism restricts a user to viewing only service requests belonging to their own organization?
- Audit trail configuration on the object
- Menu exclusion on the responsibility
- Data access scope defined on the user's role or organization assignment Correct answer.
- Password policy on the user account
Explanation
Record visibility is filtered by data access scope, which ties users to organizations or teams so queries return only permitted rows. This filter is applied in addition to privilege checks. Menus, passwords, and audit settings do not limit which records a user can retrieve.
Question 26Security, Users, Roles, and Data Access
An administrator needs to give a contractor read-only access to knowledge articles without allowing edits. What is the most appropriate approach?
- Disable the contractor's account between sessions
- Assign the contractor the same role as full-time editors and rely on training
- Assign the contractor a role that carries only the view privilege for knowledge articles Correct answer.
- Grant the contractor the system administrator responsibility
Explanation
Least privilege calls for granting exactly the privileges needed, so a role limited to viewing knowledge articles satisfies the requirement. Reusing an editor role would over-grant and create risk. Administrator responsibilities and account toggling do not address the access requirement cleanly.
Question 27Security, Users, Roles, and Data Access
Which statement about profile options in Oracle Service Center security is accurate?
- They can set defaults and behavior at site, application, responsibility, or user level Correct answer.
- They are used to define which records a user may query
- They replace roles as the primary authorization mechanism
- They are assigned to roles to grant privileges
Explanation
Profile options are hierarchical settings that control application behavior and defaults, resolved from the most specific level set. They are configuration controls, not authorization grants. Record filtering is handled by data access scope, and privileges come from roles.
Question 28Security, Users, Roles, and Data Access
A user reports that a newly granted privilege is not effective. The administrator confirms the role assignment was saved. What should be checked first?
- Whether the user session was refreshed or re-authenticated after the grant Correct answer.
- Whether the user's password meets complexity rules
- Whether the audit trail is enabled for the object
- Whether the user has a notification subscription
Explanation
Privileges are typically cached in the user's session, so changes may require a refresh or new sign-in before they take effect. Confirming the grant was saved is only half the check. Password rules, audit settings, and subscriptions do not affect privilege propagation.
Question 29Security, Users, Roles, and Data Access
Which practice best supports segregation of duties in Service Center security administration?
- Assigning all users to a single shared role
- Separating the role that configures security from the role that approves access requests Correct answer.
- Sharing one administrator account among the team
- Granting every administrator the full set of roles for convenience
Explanation
Segregation of duties requires that conflicting responsibilities be split so no single person can configure and approve the same access. This reduces the risk of unauthorized privilege escalation. Broad grants, shared roles, and shared accounts all weaken accountability and control.
Question 30Security, Users, Roles, and Data Access
What is the purpose of an audit trail in the Service Center security model?
- To automatically revoke privileges after a period of inactivity
- To define which records a user can see
- To record security-relevant events such as grants and access changes for review Correct answer.
- To encrypt data at rest in the application database
Explanation
Audit trails provide a chronological record of security-relevant activity so administrators can investigate and demonstrate compliance. They support detection and accountability rather than enforcement. Revocation, encryption, and record filtering are handled by other mechanisms.
Question 31Security, Users, Roles, and Data Access
A manager needs to approve access requests only for their own direct reports. Which configuration supports this?
- Grant the manager the security administrator role
- Grant the manager a global approval role covering all users
- Assign the manager an approval role scoped to their organization or reporting hierarchy Correct answer.
- Add the manager to every team in the system
Explanation
Approval authority should be scoped so the manager sees and acts on requests only within their organizational or hierarchical boundary. This applies the least-privilege principle to approval workflows. Global roles, administrator roles, and blanket team membership all over-grant authority.
Question 32Security, Users, Roles, and Data Access
Which combination correctly describes authentication versus authorization in Service Center?
- Authentication applies only to administrators; authorization applies only to end users
- Both terms describe the same privilege-granting process
- Authentication verifies identity; authorization determines what the identity may do Correct answer.
- Authentication determines permissions; authorization verifies identity
Explanation
Authentication establishes who the user is, typically through credentials or single sign-on. Authorization then evaluates roles and privileges to decide what that verified identity may access. The two are distinct stages and apply to all user types.
Question 33Security, Users, Roles, and Data Access
A security team wants to onboard a large group of new agents with identical access. What is the most efficient and maintainable approach?
- Create each user individually and assign privileges one by one
- Copy an existing user's entire account configuration manually
- Define a standard agent role and assign it to each new user Correct answer.
- Grant each new user the administrator responsibility temporarily
Explanation
A reusable role captures the shared privilege set once, and assigning it to each user keeps onboarding consistent and auditable. Later changes to the role propagate to all holders. Manual per-user grants and copying accounts are error-prone and hard to maintain.
Question 34Security, Users, Roles, and Data Access
Which statement about data access scope and privileges is correct when a user holds multiple roles?
- Privileges from additional roles are ignored until the first role is removed
- The narrowest scope among the roles always wins
- The user's effective access is the union of privileges and the broadest applicable scope Correct answer.
- Only the first assigned role is evaluated
Explanation
Effective access is additive: the user receives the combined privileges of all assigned roles, and visibility expands to the widest applicable scope. There is no first-role precedence or narrowest-wins rule. Administrators must therefore review the cumulative effect when stacking roles.
Question 35Security, Users, Roles, and Data Access
An administrator must prevent a support agent from exporting customer contact data while still allowing the agent to view it on screen. Which control addresses this requirement?
- Withholding the export or print privilege while retaining the view privilege Correct answer.
- Reducing the agent's data access scope to a single record
- Removing the view privilege for contact records
- Setting the agent's language profile option to a restricted value
Explanation
Privileges are granular, so viewing and exporting are separate grants. Retaining view while withholding export satisfies the requirement precisely. Removing view would block the allowed task, and profile or scope changes do not target the export action.
Question 36Security, Users, Roles, and Data Access
Which action best reduces the risk of orphaned access when an employee leaves the organization?
- Archiving closed service requests
- Relying on the employee to report departure
- Deactivating the user account and removing role assignments as part of an offboarding process Correct answer.
- Changing the site-level password policy
Explanation
Timely deactivation plus removal of role assignments closes the access path and prevents lingering privileges. An offboarding process makes this repeatable and auditable. Policy changes and archiving do not remove an individual's access.
Question 37Security, Users, Roles, and Data Access
A user in one organization needs temporary cross-organization visibility to resolve an escalation. What is the controlled approach?
- Permanently widening the user's base role to all organizations
- Granting a time-bound role or scope extension for the specific organization, then removing it Correct answer.
- Sharing another agent's credentials for the duration
- Disabling data access scope checks for the user
Explanation
Temporary needs should be met with temporary, narrowly scoped grants that are removed when the escalation ends. This preserves least privilege and leaves an auditable trail. Permanent widening, credential sharing, and disabling scope checks all create lasting risk.
Question 38Security, Users, Roles, and Data Access
Which element determines the set of functions and menus a user can navigate to after sign-in?
- The user's assigned responsibility Correct answer.
- The user's notification preferences
- The user's data access scope
- The user's password expiry date
Explanation
Responsibilities map users to menus and functions, defining the navigable surface of the application. Data access scope controls which records are visible within those functions. Preferences and password settings do not define navigation.
Question 39Security, Users, Roles, and Data Access
An auditor asks how the team ensures that only authorized personnel can change role definitions. Which control should be described?
- Role changes are approved verbally without records
- Role administration is restricted to a dedicated security administrator role with audit logging Correct answer.
- Any user with a Service Center login can edit roles by default
- Role definitions are stored in a shared spreadsheet
Explanation
Role definition changes are privileged operations and should be limited to a dedicated administrative role, with changes logged for accountability. This combination of restriction and auditability satisfies the auditor's concern. Open editing, spreadsheets, and verbal approvals lack the necessary control.
Question 40Security, Users, Roles, and Data Access
A user holds a role granting view access to all regions and a second role granting edit access only to the North region. What is the resulting effective access?
- No access because the roles conflict
- View access only in the North region
- View access to all regions and edit access only in the North region Correct answer.
- Edit access to all regions
Explanation
Privileges and scopes combine additively across roles, so the user keeps global view from the first role and gains edit within the North scope from the second. Roles do not cancel each other out on conflict. This cumulative behavior is why role stacking must be reviewed carefully.
Question 41Case and Incident Management Configuration
In Oracle Service Center case management, which field on a case record is used to group related cases into a parent-child hierarchy so that a single resolution can close the entire group?
- The severity code on the case
- The parent case reference on the child case Correct answer.
- The contact party on the case
- The category node assigned to the case
Explanation
Parent case references let agents link a case to a master case so that related issues are tracked and resolved together. The category, severity, and contact fields describe the case but do not establish hierarchy between cases.
Question 42Case and Incident Management Configuration
A service agent needs to capture the exact moment a case was reopened after a customer disputed a resolution. Which standard case attribute should be configured to record this event automatically?
- The case priority matrix
- The case owner assignment rule
- The case status history with a timestamp Correct answer.
- The case description free-text field
Explanation
Status history records each transition of a case with the user and timestamp, which is the correct audit trail for a reopen event. Description, priority, and owner rules do not preserve a chronological record of status changes.
Question 43Case and Incident Management Configuration
Which configuration determines the list of values an agent can pick when setting the channel on a new case, such as Phone, Email, or Web?
- A lookup type with its lookup codes Correct answer.
- A case category tree
- A validation set on the case number
- A workflow rule on the case status
Explanation
Channel values are stored as lookup codes under a lookup type, and the lookup type controls the selectable values. Category trees classify issues, validation sets check field formats, and workflow rules act on transitions rather than define picklists.
Question 44Case and Incident Management Configuration
An implementation team wants every new case to inherit the account's default contact as the primary contact unless the agent overrides it. Which mechanism is the appropriate place to implement this defaulting?
- A read-only field-level security setting
- A category node restriction
- A scheduled process that updates cases nightly
- A defaulting rule on the case contact field Correct answer.
Explanation
Defaulting rules populate field values at record creation and can derive the contact from the account, while still allowing an agent override. Batch jobs run too late, field security does not set values, and category restrictions only limit classification choices.
Question 45Case and Incident Management Configuration
Which object relationship best allows a single case to be associated with multiple affected assets while each asset association records its own serial number?
- A category node on the asset record
- A lookup on the asset pointing to the case owner
- A child entity linked to the case with a many-to-one relationship Correct answer.
- A single text field on the case storing comma-separated serials
Explanation
A child entity related to the case supports many asset associations, each with its own attributes such as serial number. A delimited text field cannot carry per-asset attributes, and the other options do not model multiple assets per case.
Question 46Case and Incident Management Configuration
A supervisor wants cases with severity Critical to automatically page the on-call engineer within five minutes of creation. Which two configuration elements are required to satisfy this requirement?
- A category node and a validation set
- An escalation rule with a time threshold and a notification action Correct answer.
- A status history record and a case comment
- A defaulting rule and a read-only field
Explanation
Escalation rules evaluate conditions such as severity and trigger actions after a defined time threshold, including notifications. The other combinations affect classification, validation, or audit but cannot page an engineer on a timer.
Question 47Case and Incident Management Configuration
An agent closes a case but the customer replies that the issue persists. Which configuration should the team verify to allow the case to move from Closed back to In Progress?
- The status transition model permits the reopen transition Correct answer.
- The case number sequence is reset
- The case category tree includes a Reopened node
- The contact record is set to active
Explanation
Whether a case can return from Closed to In Progress is governed by the allowed status transitions in the case status model. Category nodes, number sequences, and contact status do not control case lifecycle movement.
Question 48Case and Incident Management Configuration
Which statement accurately describes how a service-level agreement milestone is measured on a case?
- The milestone timer starts from the case creation or a defined start event and pauses or stops per configured conditions Correct answer.
- The milestone is a static text field that agents update manually
- The milestone is derived from the case category depth
- The milestone is calculated once when the case is closed and never during the lifecycle
Explanation
SLA milestones track elapsed time against targets, starting from a defined event and honoring pause or stop conditions configured for the milestone. They are not static fields, and they are not derived from category structure.
Question 49Case and Incident Management Configuration
A team needs to prevent agents from setting a case to Resolved while mandatory resolution notes are empty. Which configuration enforces this at the transition?
- A defaulting rule on the resolution notes field
- A required-field validation on the Resolved transition Correct answer.
- A read-only setting on the resolution notes field
- A category node restriction on Resolved
Explanation
Transition-level required-field validation blocks the status change until the mandatory field is populated. Defaulting would fill the field automatically, category restrictions affect classification, and read-only would prevent agents from entering notes at all.
Question 50Case and Incident Management Configuration
Which configuration object is used to define the set of fields displayed on the incident intake layout for a specific agent role?
- A lookup type assigned by role
- An escalation rule assigned by role
- A page layout assigned by role Correct answer.
- A status history view assigned by role
Explanation
Page layouts control which fields appear and their arrangement, and layout assignment can vary by role or profile. Lookup types define picklist values, escalation rules act on time and conditions, and status history is a record view rather than an input layout.