PSA-SYSADMIN Practice Questions

Certinia PSA utilizes a custom object, pseConfigurationValuec, to manage system-wide application settings and defaults. To change the default scheduling strategy for new Assignments, an administrator must locate and modify the specific Configuration Value record responsible for this setting. This record typically has a pseKeyc value such as DefaultSchedulingStrategy. By updating the pseValuec field on this record to the desired strategy (e.g., "Fixed Duration & Effort"), the administrator sets a new default for the entire organization, which will be used when creating new Assignments.

A. Removing options is accomplished by editing the picklist field on the Assignment object, which limits choices but does not set the default value.

C. Deleting the configuration record would remove the custom default, causing the system to revert to its hard-coded default, rather than setting a new one.

1. Certinia PSA Administrator Guide: The guide details the use of Configuration Options (records of the pseConfigurationValuec object) to control application behavior. The section on "Configuration Options" explains how to find and edit these records to set system defaults. Specifically, it lists keys like DefaultSchedulingStrategy that control default values for core objects like Assignments. (Reference: Certinia PSA Administrator Guide, "Configuration Options" section).

2. Certinia PSA Help Portal, "Configuration Options": This resource provides a comprehensive list of all configuration keys available in PSA. The entry for DefaultSchedulingStrategy explicitly states its purpose is to "Set the default scheduling strategy for new assignments." This confirms that modifying this specific configuration record is the correct procedure. (Reference: Certinia PSA Help, "Configuration Options" article, entry for DefaultSchedulingStrategy).

A Resource Record in Certinia PSA is the central object representing an individual who can be scheduled for and perform work on projects. Its existence is a prerequisite for two fundamental actions: being assigned to a project as a team member and tracking actuals. Assigning a resource links them to the project's work breakdown structure, making them available for tasks. Subsequently, the resource must enter timecards and expense reports against their assigned projects to record effort and costs, which is essential for project accounting, billing, and utilization tracking.

A. Creating a milestone: Creating a milestone is a project management function performed by a user with the appropriate permissions, typically a Project Manager. This action pertains to defining the project structure, not performing work that requires a Resource Record.

1. Certinia PSA Administration Guide, "Resources Overview". This section details that a resource record must be created for any user who needs to be assigned to a project, have their time and expenses tracked, or be included in resource planning and utilization calculations.

2. Certinia PSA Project Management Guide, "Building Your Project Team". This chapter explicitly states that to add a person to a project team, you must select them from the list of active Resource records in the system. The assignment process is fundamentally dependent on the existence of a Resource record.

3. Certinia PSA Time and Expense Management Guide, "Entering Timecards". The guide specifies that only users with an associated Resource record can create and submit timecards. The system links the timecard entry to the resource, their assignments, and the corresponding project for accurate cost and revenue recognition.

The requirement is to present different navigation options within the "Services Delivery Workspace" based on a user's team. This can be accomplished using standard Salesforce Lightning App Builder functionality.

One valid method (C) is to place multiple instances of the "FF Navigation" component onto a single Lightning page. Each component instance is configured with the navigation links for a specific team. Then, Component Visibility rules are applied to each instance, using user attributes like Profile, Role, or a custom field indicating their team, to ensure only the relevant component is displayed to the user.

Another valid method (B) is to clone the entire Lightning page. Each cloned page would contain a single "FF Navigation" component configured for a specific team. The page variations are then assigned to different user profiles or audiences, effectively showing a different page layout to each team.

A. The "FF Navigation" component's configuration focuses on defining navigation sections and links, not on conditional logic for hiding them. This type of dynamic visibility is a platform feature handled by Component Visibility rules.

1. Salesforce App Builder Documentation (Supports C): The Lightning App Builder allows administrators to set visibility filters on components. This feature, often referred to as Dynamic Lightning Pages, enables a component to appear only when specified criteria are met, such as a user's profile or a field value on a record. This directly supports adding the component twice and controlling visibility.

Source: Salesforce Help & Training, "Dynamic Lightning Pages", Component Visibility Filters section.

2. Salesforce Page Assignment Documentation (Supports B): Lightning pages can be assigned to specific combinations of apps, record types, and profiles. By cloning a page and customizing it for a specific team's profile, an administrator can ensure that team sees a unique page layout.

Source: Salesforce Help & Training, "Activate Lightning Experience Record Pages", Assign Record Pages to Profiles section.

3. Certinia PSA Documentation (Context for A): The configuration options for the "fflibnavigation" (FF Navigation) component within the Lightning App Builder focus on defining the Navigation Items and Section Titles. The documentation does not specify a built-in property like "Hide Navigation Sections" for conditional rendering based on user attributes; instead, it relies on the underlying Salesforce platform's visibility features.

Source: Certinia PSA System Administration Guide, "Configuring the Services Delivery Workspace" section.

In Certinia PSA, 'Actuals' are records that store the financial results of transactions based on historical business events. They are calculated and aggregated over specific time periods. The standard set of Actuals tracked includes Bookings (value of signed contracts), Billings (value of invoices), Revenue (recognized income), Costs (incurred expenses), and Margin (the difference between revenue and costs). These components provide a comprehensive view of a project's or resource's financial performance based on what has already occurred, as opposed to what is planned or forecasted.

A. This option is incorrect because 'Budgets' are planned financial targets or limits set for a project. They represent a plan, not the actual historical results of transactions.

B. This option is incorrect because 'Forecasts' are predictions or estimates of future financial performance. They are forward-looking and distinct from 'Actuals', which are backward-looking records of completed transactions.

1. Certinia PSA Documentation, "Actuals Overview": This document explicitly defines Actuals and lists their components. It states, "Actuals include: Bookings, Billings, Revenue, Costs, Margin, Billed Revenue, and Unbilled Revenue." This directly supports the components listed in the correct answer.

2. Certinia PSA Documentation, "Financial Management Guide", Section: Key Financial Metrics: This guide details the core financial concepts in PSA. It differentiates between actuals (historical data like revenue and cost), budgets (planned data), and forecasts (projected data), reinforcing that budgets and forecasts are not part of the Actuals object records.

3. Certinia PSA Documentation, "Reporting Guide", Section: Actuals Datasets: This section describes the standard reporting datasets built on the Actuals object. The available fields and measures in these datasets correspond directly to Bookings, Billings, Revenue, Costs, and Margin, confirming these are the primary components of Actuals.

Certinia PSA utilizes a custom object named "Permission Control" to manage granular, application-specific permissions for users. These permissions govern functional capabilities that are not controlled by standard Salesforce profiles or permission sets. To allow a user to create or enter a Resource Request, an administrator must navigate to the user's associated Permission Control record and enable the "Resource Request Entry" checkbox. If a Permission Control record does not exist for the user, one must be created.

A. Assign the Resource Request Entry Permission Set.

This is incorrect. While Certinia provides permission sets for object and field-level security, specific functional permissions like entering a resource request are controlled via the Permission Control record, not a dedicated permission set.

C. Ensure the Resource Request Entry checkbox is selected on the User.

This is incorrect. The checkbox for this specific permission is located on the related Permission Control custom object record, not directly on the standard User object record.

1. Certinia PSA Administrator Guide: In the section "Permission Controls," the documentation details the purpose of the Permission Control object. It states, "Permission controls give you a granular level of control over the actions that your resources can perform in PSA." It explicitly lists "Resource Request Entry" as one of the checkboxes on this object that grants the ability to create resource requests. (Reference: Certinia PSA Documentation, "Permission Controls Overview").

2. Certinia PSA Help Portal: The article "Setting PSA User Permissions" outlines the necessary steps for user setup. It specifies that after assigning a license and a base permission set, a Permission Control record must be created or edited for the user to grant functional permissions. The "Resource Request Entry" permission is cited as a key example of a permission granted in this manner. (Reference: Certinia Help Center, Article ID: 00021345, "PSA Permissions Fields").

The Project Management Workspace (PMW) is primarily designed for project managers to view and manage the projects they are responsible for. The default view, "My Projects," filters the project list to show only those projects where the logged-in user is the value in the Project Manager lookup field on the Project record. If a user is not assigned as the Project Manager on any projects, this default view will correctly display no records, leading to the reported issue.

B. The user is missing the Project Management Workspace Permission Control: If the user were missing this permission control, they would be unable to access or view the Project Management Workspace page or component at all.

C. The user is missing the PSA - Project Manager Permission Set: Lacking this permission set would result in more fundamental access errors, such as "Insufficient Privileges," preventing the user from seeing project data, rather than simply seeing an empty list.

1. Certinia PSA Documentation, "About the Project Management Workspace": This document states, "The Project Management Workspace (PMW) provides a centralized location for project managers to view and manage their projects." It further details that the default "My Projects" filter displays projects where the current user is the designated Project Manager. (Reference: help.certinia.com, Project Management > Project Management Workspace > About the Project Management Workspace).

2. Certinia PSA Documentation, "Permission Controls": This section explains that Permission Controls are used to grant or deny access to specific application features and UI elements. The "Project Management Workspace" permission control specifically governs access to the workspace tab. A user without this permission would not be able to navigate to the page. (Reference: help.certinia.com, PSA Administration > Permissions > Permission Controls).

Certinia PSA is designed to accommodate diverse global work schedules by allowing the creation of multiple, distinct work calendars. The correct and most efficient method is to create a specific work calendar that accurately reflects the 35-hour work week for French employees. This calendar can then be associated directly with the relevant resource records. This approach ensures that all system calculations, including resource capacity, availability for scheduling, and utilization metrics, are precise. It also provides the flexibility to add region-specific holidays, ensuring accurate project planning and resource management for that specific group.

A. This is incorrect because the premise that PSA only allows one work calendar is false. The platform is designed to support multiple calendars for different regions or working arrangements.

B. This is incorrect because it introduces data inaccuracies. The work calendar is a foundational element for capacity, scheduling, and forecasting, not just a variable for manual utilization calculations.

1. Certinia PSA Administration Guide: The section on "Work Calendars" explicitly details the process for creating and managing multiple calendars. It states, "You can create multiple work calendars to reflect the different working patterns of your resources." The guide further explains how to set the hours per workday and associate the calendar with specific resources, regions, practices, or groups. (Refer to the "Setting Up Work Calendars" and "Associating Work Calendars" sections in the official documentation).

2. Certinia PSA Resource Management Documentation: This documentation outlines that the Work Calendar field on the Resource object is a lookup to the Work Calendar object. This object relationship is fundamental to the system's design, allowing each resource to be assigned a specific calendar that dictates their capacity and availability, directly supporting the methodology described in the correct answer. (Refer to the "Resource Object Fields" section).

The most effective strategy for a system administrator to stay current with Certinia (formerly FinancialForce) PSA involves leveraging a mix of official resources. The Certinia Community is the central hub for release announcements, discussions, and documentation access. Release previews and webinars provide guided demonstrations of new functionality directly from the vendor. Official PSA documentation offers in-depth technical details for configuration and use. Finally, Certinia-specific Trailhead modules provide structured, hands-on learning paths for mastering new features and platform capabilities, which is a key part of their modern enablement strategy. This combination ensures a comprehensive and practical understanding of product updates.

A. The official Salesforce user group is too general; it focuses on the core Salesforce platform, not the specific features and components of the Certinia PSA managed package.

C. The CertiniaX Summit (formerly FinancialForceX) is a major annual conference, not a regular, ongoing resource for learning about the specific features included in every product release cycle.

1. Certinia Community: The official hub for product information, release readiness, and documentation. The "Release Information" section is the primary source for release notes, previews, and webinar schedules. (Source: Certinia Community Portal, Release Information section).

2. Certinia Documentation: The official product documentation is the definitive source for all feature details. For example, the "What's New" section in each release's documentation provides a detailed breakdown of enhancements. (Source: Certinia PSA Documentation, Release Notes > What's New section for any given release).

3. Certinia on Trailhead: Certinia officially provides and promotes Trailhead modules for learning its products. This is a key part of their training and certification strategy for administrators and users. (Source: Salesforce AppExchange, Certinia PSA Listing > "Learn More with Trailhead" section).

Certinia PSA provides three primary, centralized user interfaces known as workspaces, each tailored to a specific role or function within a services organization. These are the Services Delivery Workspace, offering a high-level business overview; the Project Management Workspace, for detailed project planning and execution; and the Resource Management Workspace, for managing resource allocation, availability, and skills. These workspaces consolidate key data, metrics, and actions into a unified view to enhance efficiency and decision-making for their respective users.

B. "Task Planning Workspace" is not a named workspace; task planning is a feature conducted within the Project Management Workspace.

C. "Milestone Forecast Workspace" is not a standard workspace; milestone forecasting is a capability, not a dedicated top-level interface.

1. Certinia PSA Documentation, "PSA Workspaces Overview". This document explicitly lists and describes the three available workspaces. It states, "PSA provides the following workspaces: Services Delivery Workspace... Project Management Workspace... Resource Management Workspace..." (Accessed via Certinia's official help portal).

2. Certinia PSA Documentation, "Project Management Workspace". This section details the components and functions of the Project Management Workspace, which includes Gantt charts and task management, confirming that "Task Planning" is a function within it, not a separate workspace. (Accessed via Certinia's official help portal).

The Certinia PSA application includes a specific configuration setting named Assign Project Manager To Timecard Approver within the Timecard Entry settings. When this checkbox is set to True, the system automatically assigns the Project Manager from the timecard's primary project as the approver. This built-in PSA configuration takes precedence over custom automation, such as the described Flow. Therefore, even though a Flow is designed to assign the resource's manager, this system-level setting overrides it, resulting in the timecard being routed to the Project Manager for approval.

A. PSA requires that only Project Managers can approve Timecards: This is incorrect. Certinia PSA's approval processes are flexible and can be configured to route to various individuals, including a resource's direct manager or a designated approver.

B. The process builder to assign the resource's manager is not active: The question specifies a Flow, not a Process Builder. Even if the automation were inactive, it wouldn't explain why the approver consistently defaults to the Project Manager; another mechanism must be responsible.

1. Certinia PSA Administration Guide: In the section "Timecard Entry Settings", the guide details the configuration options available for timecards. It explicitly describes the Assign Project Manager To Timecard Approver checkbox and its function: "If selected, the project manager on the project is assigned as the timecard approver." This confirms that the setting directly causes the behavior described in the question.

2. Certinia PSA Help Portal, "Timecard Approval Process": This documentation outlines the standard approval mechanisms. It clarifies that approvals can be managed through standard Salesforce approval processes, which can be customized to route to different approvers based on various criteria, disproving the notion that only Project Managers can approve timecards. The documentation implicitly supports that a specific configuration (like option C) would be needed to enforce a single approver type.