CTA Practice Questions

To streamline application deployment and ensure consistency across multiple instances, the CTA

should prioritize recommending the use of the Application Repository to centralize and distribute

custom apps.

Here's why:

Centralized Repository: The Application Repository provides a central location to store and manage

custom applications.

Version Control: It allows for versioning of applications, making it easier to track changes and roll

back if needed.

Easy Distribution: Applications can be easily published and distributed to other instances from the

repository.

Consistency: Using the repository helps ensure that all instances have the same version of an

application, promoting consistency and reducing conflicts.

Why not the other options?

A . Use it for a Citizen Development program: While the repository can support citizen development,

it's not its primary purpose in this scenario.

B . Employ it for real-time collaborative coding: The repository is not designed for real-time

collaborative coding.

D . Use it as a backup for all global application packages: While it can be used for backups, its primary

benefit here is for centralized management and distribution.

Reference: ServiceNow Application Repository documentation

Thank you for your visit.

A ServiceNow governance framework provides structure and guidance for managing the platform

and its applications. It typically defines:

A . How decisions are made: The framework outlines the processes for making decisions related to

the platform, such as changes to configurations, new application development, and platform

upgrades. This might include approval processes, escalation procedures, and communication

protocols.

B . What decisions need to be made: The framework identifies the types of decisions that require

governance oversight. This might include decisions about platform strategy, architecture, security,

data management, and integration with other systems.

C . Who is involved in decision-making: The framework establishes roles and responsibilities for

different stakeholders in the governance process. This might include defining a governance board,

steering committees, and individual roles with specific decision-making authority.

Why not the other options?

D: While recurring schedules for governance meetings are important, they are not a defining

element of the governance framework itself. The framework focuses on the overall structure and

processes for decision-making.

E: How work gets done on the platform is more related to process definitions and workflows within

specific applications, not the overarching governance framework.

Reference: ServiceNow Governance, Risk, and Compliance documentation, ITIL 4 framework

Service Mapping in ServiceNow has two primary capabilities:

A . Create a service-centric Configuration Management Database (CMDB): Service Mapping helps

shift the focus of the CMDB from individual components to a service-centric view. It achieves this by

mapping the relationships between infrastructure components and the services they support,

providing a clear understanding of how IT supports business services.

E . Establish links between IT infrastructure components and application services: This is the core

function of Service Mapping. It automatically discovers and maps the dependencies between

applications, infrastructure (servers, databases, network devices), and the services they deliver. This

creates a visual representation of the IT landscape and how it supports business services.

Why not the other options?

B: While Service Mapping can indirectly contribute to cybersecurity by providing visibility into the IT

environment, enhancing cybersecurity measures is not its primary function.

C: Automating routine IT infrastructure updates is typically handled by other ServiceNow capabilities

like Orchestration, not Service Mapping.

D: Software licensing management is usually handled by Software Asset Management tools, not

Service Mapping.

Reference: ServiceNow Service Mapping documentation

To control access to sensitive data at the field level, the system administrator should use Column

Level Encryption (CLE).

Here's how CLE works:

Field-Level Encryption: CLE allows you to encrypt specific fields within a table, ensuring that only

authorized users with the necessary decryption keys can access the data.

Granular Control: You can define different encryption keys for different fields or groups of fields,

providing fine-grained control over data access.

Role-Based Access: You can grant access to decryption keys based on user roles, ensuring that only

authorized personnel can view sensitive information.

Why not the other options?

A . PI1 Encryption: This is not a standard ServiceNow encryption feature.

C . Cloud Encryption: This is a broader term for encryption solutions provided by cloud providers, not

a specific ServiceNow feature.

D . Full Disk Encryption (FDE): This encrypts the entire hard drive, not individual fields within the

application.

Reference: ServiceNow Column Level Encryption (CLE) documentation

The primary purpose of analyzing an organization's existing architecture as a Certified Technical

Architect (CTA) is to identify issues and gaps in the system. This analysis helps to:

Understand the Current State: Gain a clear picture of the current architecture, including its

components, integrations, and limitations.

Identify Pain Points: Pinpoint areas where the architecture is not meeting business needs or causing

challenges.

Assess Risks: Evaluate potential risks and vulnerabilities within the architecture.

Inform Recommendations: Provide a basis for making recommendations for improvements and

future architecture planning.

Why not the other options?

A . To evaluate existing system performance: While performance is important, it's one aspect of the

broader architectural analysis.

C . To recommend a product roadmap: A product roadmap might be an outcome of the analysis, but

the primary purpose is to understand the current state and identify areas for improvement.

D . To evaluate existing testing practices: Testing practices are important, but they are not the

primary focus of architectural analysis.

Reference: ServiceNow CTA exam blueprint, Architectural analysis best practices

Non-functional testing focuses on how a system operates and meets user expectations in terms of

qualities like:

Performance: Response times, load handling, scalability

Usability: Ease of use, user interface design

Security: Protection against unauthorized access and data breaches

Reliability: System stability and availability

Maintainability: Ease of making changes and updates

Why not the other options?

A . Specific behaviors and outputs of the system: This is the focus of functional testing, which verifies

that the system does what it's supposed to do.

C . The creation of records and setting field values: This is a specific functional aspect of the system.

D . Functional requirements outlined in the design document: These are tested during functional

testing.

Reference: Software testing best practices, ISTQB Foundation Level syllabus

The primary factor in determining the number of MID Servers needed is the number of targets and

interaction frequency.

Targets: The number of devices, applications, or external systems that ServiceNow needs to interact

with (e.g., for discovery, orchestration, integrations).

Interaction Frequency: How often ServiceNow needs to communicate with these targets (e.g.,

continuous monitoring, scheduled data imports).

Why not the other options?

A . The number of network routers in use: While network infrastructure is important, it's not the

primary factor for MID Server sizing.

C . The number of concurrent users on the instance: User activity impacts application server load, not

directly the number of MID Servers needed.

D . The geographical spread of the organization: Geographic spread can influence MID Server

placement, but the primary factor is the number of targets and interaction frequency.

Reference: ServiceNow MID Server documentation

Effective testing provides several key benefits:

B . Conforms to specifications as defined in stories: Testing ensures that the developed software

meets the requirements and acceptance criteria outlined in user stories or other requirement

documents.

D . Validates new functionality without introducing regressions: Testing verifies that new features or

changes work as expected and do not negatively impact existing functionality (regressions).

E . Identifies defects early in the development process: The earlier defects are found, the cheaper

and easier they are to fix. Testing helps identify issues early in the development lifecycle.

Why not the other options?

A . Ensures compliance with industry standards: While testing can help with compliance, it's not the

primary goal. Compliance often involves specific audits and assessments.

C . Enhances overall system performance: Performance testing is a specific type of testing that

focuses on system performance, but it's not a general benefit of all testing.

Reference: Software testing best practices, ISTQB Foundation Level syllabus

In the final planning stage of a ServiceNow integration, the CTA should prioritize assessing network

and system communication needs. This involves:

Connectivity: Verifying network connectivity between ServiceNow and the external system. This

includes checking firewalls, ports, and any required network configurations.

Protocols: Determining the communication protocols to be used (e.g., REST, SOAP, JDBC).

Security: Ensuring secure communication channels, including authentication and encryption

requirements.

Performance: Considering bandwidth requirements and potential performance impacts on both

systems.

Why not the other options?

B . Determining the color scheme for integration UI: While UI considerations are important, they are

not the primary focus during the technical details gathering stage.

C . Planning the communication for the integration go-live: Communication planning is important but

separate from the technical details of the integration itself.

D . Estimating the projected integration data metrics: Data volume estimates are useful, but the

primary focus is on ensuring successful communication between the systems.

Reference: ServiceNow integration best practices, Network communication fundamentals

In a multi-development environment stack in ServiceNow, the types of splits commonly refer to how

development efforts are organized and managed across different environments.

Product-based splits:

Development efforts are divided based on specific products or modules. For instance, one team may

work on ITSM while another works on ITOM.

Release-based splits:

Development is split by different release versions. Teams may work on different versions of the same

product for testing, updates, or new features.

These splits help manage concurrent development efforts efficiently, especially in environments with

multiple teams and priorities.