Free GCP-GC-IMP Practice Test

When configuring an external SIP trunk in Genesys Cloud, the administrator must specify the transport layer protocol for SIP signaling. The platform provides three distinct options for this configuration: TCP (Transmission Control Protocol), a reliable connection-oriented protocol; UDP (User Datagram Protocol), a connectionless best-effort protocol; and TLS (Transport Layer Security), which provides encrypted communication over TCP. These selections are available in the "Transport" list within the trunk's protocol settings.

A. The default protocol: This describes a pre-selected setting (which is TLS), not a distinct protocol type that can be chosen from the list of available transport options.
D. SIP: SIP (Session Initiation Protocol) is the application-layer protocol being transported, not the transport-layer protocol itself. You select a transport (TCP, UDP, TLS) for SIP.

1. Genesys Cloud Resource Center, "Create an external trunk."

Reference: In the section titled "Configure the transport protocol," the documentation states: "Under the Protocol section, from the Transport list, select the transport protocol that you want to use for this trunk. You can select TLS, TCP, or UDP. The default is TLS." This directly confirms the three selectable transport protocols.

Source: https://help.mypurecloud.com/articles/create-an-external-trunk/ (Accessed under the "Configure an external trunk" procedure).

In Genesys Cloud, before an extension can be assigned to a user, it must first exist as a configurable object within the system. The standard administrative procedure for creating multiple extensions is to define and generate an extension pool. This pool acts as a repository of available, pre-configured extensions. Once the pool is created, individual extensions from that pool can be allocated and assigned to users, phones, or other system entities like IVR menus. This creation step is a mandatory prerequisite for the assignment process.

B. Buy the extension number from the carrier. Extensions are internal to the Genesys Cloud organization's private telephone network; they are not purchased from public carriers.
C. Add the extension to the dial plan. A dial plan determines call routing for existing numbers. The extension must be created before it can be referenced in a dial plan.
D. Assign the extension to the user's phone. An extension is assigned to a user, not directly to a phone. The user then logs into a phone (physical or softphone) to use their assigned extension.

1. Genesys Cloud CX Resource Center, "Create an extension pool": This document outlines the procedure for creating a range of extensions. The overview states, "Create an extension pool to generate a range of extensions that you can assign to users, IVR systems, managed phones, or campaigns." This confirms that creating the pool is a precursor to assignment.

2. Genesys Cloud CX Resource Center, "Assign an extension": This guide details the assignment process. The first sentence of the procedure is, "You can assign an existing extension to a user, phone, or workgroup." This explicitly states that the extension must already exist before it can be assigned.

3. Genesys Cloud CX Resource Center, "About number plans": This document explains how numbering plans work, including extension ranges. It notes, "The number plan defines the valid range of internal extension numbers for your organization." This definition of the valid range (often done via an extension pool) is a foundational step before individual extensions can be used or assigned.

When a video call is initiated in a Genesys Cloud chat room, a video meeting interface is launched. For all individuals to participate, including the initiator, they must each take an explicit action within this video interface. After the initial click to start or join the call from the chat room, each user is presented with a preview screen. On this screen, they can configure their camera and microphone settings and must then click the "Join" button to formally enter the live video session. This step is required for every participant.

A. Other participants clicking the "Open video call" icon would attempt to start new, separate video calls, not join the one already in progress.
C. This is incomplete. While non-initiators click a "Join" button in the chat view, all participants, including the initiator, must complete a final "Join" action in the video view.
D. Joining a video call is an explicit user action. Participants are never automatically placed into a video session upon entering a chat room.

1. Genesys Cloud CX Resource Center, "Video meetings overview." This document describes the standard user experience for joining any video meeting. It shows a pre-join screen where users configure their devices and states, "When you join a video meeting, you can configure your camera and microphone settings before you enter the meeting." A prominent "Join Meeting" button is displayed, which must be clicked to enter. This applies to all participants, regardless of how they accessed the meeting link or notification.

2. Genesys Cloud CX Resource Center, "Start a video chat in a chat room." This article details the initiation process. The initiator clicks the Video icon to start the process, which leads to the video meeting interface. It also notes, "To join the video chat, other members of the room click Join." This initial "Join" button in the chat banner for other users also directs them to the same video meeting interface where the final join action described in the "Video meetings overview" must be completed.

In Genesys Cloud, an External Trunk is the specific configuration object used to establish a SIP connection to an external entity. An AudioCodes Mediant gateway functions as a Session Border Controller (SBC) or media gateway, which is considered an external SIP device from the perspective of the Genesys Cloud platform. This trunk type is designed precisely for interoperability with third-party gateways, SBCs, and SIP carriers to route calls between Genesys Cloud and the external system (e.g., the PSTN or a legacy PBX).

B. Network interface trunk: This is not a valid trunk type in Genesys Cloud. Network interfaces are configured on Edge appliances for network connectivity, but the logical SIP connection is defined as a trunk.
C. WebRTC phone trunk: This trunk type is used exclusively for managing connections from Genesys Cloud's native WebRTC softphones and is not intended for gateway or carrier interconnection.
D. SIP phone trunk: This is used to connect and manage generic third-party SIP phones directly with Genesys Cloud, not for establishing a connection to a gateway or SBC.

1. Genesys Cloud Resource Center, "About trunks": This document outlines the different trunk types available in Genesys Cloud. It explicitly states, "External trunks are for connections to a SIP carrier, a gateway, a session border controller (SBC), or another PBX." This directly confirms that an external trunk is the correct choice for an AudioCodes gateway.

2. Genesys Cloud Resource Center, "Create an external trunk": The introductory paragraph of this guide specifies the use case: "To create an external trunk, you must first add a new external trunk and then configure it for use with a SIP carrier, a gateway, a session border controller (SBC), or another PBX." This reinforces the purpose of the external trunk.

3. Genesys Cloud Resource Center, "Trunk configuration settings": In the section detailing External Trunk settings, the documentation describes parameters like "Outbound SIP Servers or Gateways," which are necessary for defining the connection to devices like the AudioCodes Mediant gateway.

Core Services represent the foundational logic and data management layer of the Genesys Cloud platform. This component is responsible for the "brains" of the contact center, managing essential configurations, user directories, presence states, and the business logic for routing interactions and assigning them to the appropriate agents. The functions listed—account configuration, directory search, user membership, call routing, and agent assignment—are all central to this core layer.

A. Public Interface Services: This layer serves as the entry point for all external clients and applications via the Public API, but it does not manage the underlying business logic or configuration data itself.
C. Communication Services: This component is responsible for handling real-time media and signaling protocols (e.g., SIP, WebRTC), but not the logical decisions of where to route a call or who to assign it to.
D. Application Services: These are higher-level applications, such as Workforce Management or Quality Management, that are built on top of and consume the functionalities provided by the Core Services.

1. Genesys Cloud Resource Center, "Genesys Cloud architecture overview": This document describes the platform's microservices architecture. It states, "The core services are the brains of Genesys Cloud. Core services include directory, presence, routing, and agent assignment." This directly maps the functions in the question to Core Services. (Accessed under the "Platform architecture" section).

2. Genesys Cloud Developer Center, "Platform Client SDKs": The documentation for platform APIs and SDKs is organized around these service categories. The APIs for managing users, queues, and routing logic are categorized under platform/core functionalities, distinct from APIs for communication control or higher-level applications. This structure reinforces the separation of concerns where Core Services handle the listed functions.

The Genesys Cloud CX platform's Documents feature allows users to select and upload multiple files simultaneously into a workspace. When a user initiates an upload, the system's file selection dialog box enables the selection of more than one file at a time, streamlining the process of adding content to a workspace.

The "False" option is incorrect because the user interface for uploading documents to a Genesys Cloud CX workspace explicitly supports multi-file selection. Limiting users to single-file uploads would be inefficient and is contrary to the documented functionality of the platform.

1. Genesys Cloud CX Resource Center, "Upload a document to a workspace".

Section/Step: Procedure, Step 4.

Content: "In the Upload Documents dialog box, click Select Files. Navigate to and select the files you want to upload. You can select multiple files." This directly confirms the capability.

2. Genesys Cloud CX Resource Center, "About documents".

Section: Overview.

Content: This document describes the feature as a content management system for workspaces, which inherently supports efficient management tasks like bulk uploads. It states, "With documents, you can upload and manage files in a workspace." The management of "files" (plural) implies support for operations on multiple items.

Genesys Cloud CX is designed to support complex telephony environments, which includes the ability to configure multiple outbound routes. This functionality allows an organization to direct outbound calls through different trunks based on various criteria, such as the dialed number pattern (for example, routing international calls through one carrier and local calls through another), cost optimization, or for redundancy and failover purposes. The system evaluates these configured routes in a specific order of priority to select the appropriate path for an outbound call.

The "False" option is incorrect because limiting a contact center to a single outbound route would severely restrict its ability to manage outbound calling efficiently and cost-effectively. Modern contact center platforms require the flexibility to handle diverse calling scenarios, which necessitates the use of multiple, conditional outbound routes.

1. Genesys Cloud CX Resource Center, "About outbound routing." This document explains the core concept: "Outbound routing allows you to route outbound calls through a specific trunk based on a combination of a phone number and an outbound route... Genesys Cloud evaluates the outbound routes in order from top to bottom." The concept of evaluating routes "in order" inherently implies the existence of more than one route.

2. Genesys Cloud CX Resource Center, "Outbound routes page." This page describes the user interface for managing outbound routes, stating, "The Outbound Routes page displays a list of all outbound routes that have been configured for your organization." The interface is explicitly designed to display a "list" of routes, confirming that multiple entries are supported.

3. Genesys Cloud CX Resource Center, "Create an outbound route." This article provides a step-by-step procedure for adding a new outbound route to the system. The existence of a process to "create" and add a route to the configuration confirms that the system is not limited to a single, predefined route.

The statement is correct. Genesys Cloud Platform provides several hierarchical methods to set and override the Calling Name and Address (Caller ID) for outbound calls. While a default Calling Name and Address can be configured at the external trunk level, this setting can be superseded by more specific configurations within Architect flows, Outbound Dialing campaigns, or even at the individual user/station level. This allows for dynamic and context-sensitive presentation of caller ID information based on the specific business need or call scenario.

The "False" option is incorrect because the Calling Name and Address are not static values. The platform is explicitly designed to allow these attributes to be overridden at multiple points in the call-handling process, providing essential flexibility for contact center operations.

1. Genesys Cloud Resource Center, "External trunk settings": In the documentation for configuring an external trunk, under the "Calling" tab section, it describes the "Calling Address" and "Calling Name" fields. The help text explicitly states, "This value can be overridden in other places, for example, in an Architect flow." This directly confirms that the trunk-level setting is a default that can be overridden.

2. Genesys Cloud Resource Center, "Set the caller ID for outbound calls": This article provides an overview of how caller ID is managed. It states, "You can override the default caller ID number for outbound calls made from Architect call flows." It details the hierarchy of settings, confirming that Architect flows can override trunk and site-level configurations.

3. Genesys Cloud Resource Center, "Bridge action": The documentation for the "Bridge" action within Architect shows configurable fields for "Caller ID Address" and "Caller ID Name". The description for these fields indicates their purpose is to "Specify the phone number/name to use as the caller ID for the outbound call," which is a direct mechanism for overriding any pre-existing defaults for that specific call transfer.

4. Genesys Cloud Resource Center, "Create a new campaign": In the configuration settings for an Outbound Dialing campaign, there are specific fields for "Caller Name" and "Caller Number". The documentation explains that these fields are used to "Enter the name/number to display as the caller ID for this campaign." This demonstrates another level where the default trunk Calling Name and Address are overridden for a specific purpose.

The statement is true due to two primary factors: the underlying transport costs and operational efficiency. First, instant messaging leverages data networks (IP-based), where the cost per message is typically negligible and often bundled into overall data or platform subscription fees. In contrast, long-distance phone conversations, particularly those terminating on the Public Switched Telephone Network (PSTN), incur per-minute carrier charges that accumulate over the duration of the call. Second, from an operational standpoint in a contact center environment, a single agent can manage multiple concurrent messaging conversations, whereas a voice call requires an agent's dedicated, one-to-one attention. This ability to handle interactions in parallel significantly lowers the effective labor cost per interaction for messaging compared to voice.

The alternative, "False," is incorrect. It would imply that instant messaging costs are comparable to or greater than long-distance calls. This contradicts the fundamental cost structures of both IP-based data transmission and traditional telephony, as well as the established operational efficiencies gained in contact centers by shifting interactions from synchronous voice to asynchronous or concurrent digital channels. While specific pricing plans can vary, the general economic and operational model overwhelmingly favors messaging as the lower-cost channel.

1. Genesys Official Documentation: In the whitepaper "The Business Case for Asynchronous Messaging," Genesys outlines the economic benefits of messaging. It states, "Because conversations are asynchronous, agents can handle multiple customers at the same time... This increases agent productivity and reduces the cost per interaction." This directly supports the operational efficiency argument that lowers overall costs.

Source: Genesys. (2022). The Business Case for Asynchronous Messaging. Whitepaper, Page 4, Section: "Reduce Costs."

2. Genesys Official Documentation: The Genesys Cloud CX pricing model inherently demonstrates this cost difference. Voice services (Genesys Cloud CX Voice) are billed on a per-minute basis for PSTN usage, with rates varying by country. In contrast, digital channels like web messaging are typically included in the per-user license fee, and carrier-dependent messages (SMS) are billed at a low, flat rate per message segment. A multi-minute phone call will almost invariably cost more in direct carrier fees than a messaging conversation of equivalent substance.

Source: Genesys Cloud CX Resource Center. "Genesys Cloud CX Voice pricing" and "SMS pricing" articles. A direct comparison of the rate tables in these documents confirms the significant cost differential.

3. Academic Publication/Industry Research: Research on contact center operations consistently validates the lower cost-to-serve of digital channels. A study by The Aberdeen Group, a peer-respected technology and market research firm, found that the average cost per interaction for a voice call was significantly higher than for a chat or messaging interaction. This is a widely accepted benchmark in the industry.

Source: The Aberdeen Group. (2019). The ROI of Digital Customer Service. Research Report. The report quantifies the cost per contact across channels, showing voice as the most expensive real-time channel. For example, data from such reports often places the cost of a voice call at several dollars, while a chat or messaging session costs significantly less.

The most secure and administratively sound procedure for offboarding a user in Genesys Cloud is to first deactivate their account. Deactivation immediately revokes all login privileges and access tokens, effectively securing the system from the former user. It also releases the user's license for reallocation. The practice of waiting for a period, such as 30 days, before permanent deletion allows for an orderly transition, ensuring that any necessary data (call recordings, interaction history) associated with the user can be audited or transferred before it is permanently disassociated upon deletion. This two-step process balances immediate security with data retention best practices.

A. Resetting the user’s password is an insufficient security measure as it does not revoke active sessions or API tokens and leaves the account enabled.
B. Renaming the user account is an administrative action that has no effect on the user's access rights or security status.
D. Creating a role for former users and leaving the account active is a poor security practice; the account remains a potential vulnerability and continues to consume a license.

1. Genesys Cloud Resource Center, "Deactivate or reactivate a user." This document states, "When you deactivate a user, the user can no longer log in to Genesys Cloud... Deactivating a user frees a license for another user." This supports the first and most critical step in option C for immediate security.

2. Genesys Cloud Resource Center, "Delete a user." This article clarifies the finality of deletion and implicitly recommends deactivation as a less permanent alternative. It states, "When you delete a user, Genesys Cloud permanently removes the user from your organization... Before you delete a user, consider deactivating the user instead. When you deactivate a user, the user can no longer log in to Genesys Cloud, but the user’s data remains in the system." This supports the two-phase approach of deactivating first, then deleting after a consideration period.