ServiceNow CIS-DF Exam Prep
Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (Page 3 )

• Correct options: C and D — Support Group and Owned by Group.

• Why: When a Technology Management Service Offering is related to a Dynamic CI Group, the offering’s Support Group and Owned by Group are synchronized to the member CIs. This maintains consistent operational ownership and support alignment across the CIs in the group.

• Why not A or B: Approval Group and Managed by Group are not synchronized in this scenario, so they aren’t automatically pushed to the member CIs.

• Answer: Assignment group (field: assignment_group)

• Why: The scenario describes auto-populating a base system field on the Incident form when a CI is selected. If the CI has its Change Group defined (i.e., the CI’s support ownership), ServiceNow will auto-set the incident’s Assignment Group to match that CI’s supported group. This ensures the incident is routed to the appropriate team. The other options (Managed by group, Approval group, Change group) are not the fields typically auto-populated in this specific CI-initiated routing scenario.

• VPC: A logically isolated virtual network within a public cloud.
• NFV: Replaces dedicated network appliances with virtualized network functions.
• SaaS: Software delivered over the internet as a service. This application could be delivered as SaaS, but the key detail in the question is that it serves multiple user groups or tenants.

• Group1 — security-enabled: Eligible.
• Group2 — mail-enabled and security-enabled: Eligible because it is still a security group.
• Group3 — Microsoft 365 group: Not eligible for group-based licensing.
• Group4 — Microsoft 365 group, not security-enabled: Not eligible.

• Undefined or blank values
• Relationship matching problems
• Duplicate or conflicting keys
• Errors when querying the model

• Normalize all values to upper- or lowercase in the source query or Power Query.
• Add an index or surrogate key when values that differ only by case must remain distinct.

• Training data for potential bias before model training
• Trained models for bias in predictions
• Model features to help explain how they influence predictions

• A: RAG workflows are typically built using services such as Amazon Bedrock, knowledge bases, and data sources.
• B: Monitoring model quality in production is primarily associated with SageMaker Model Monitor.
• C: Documenting model details is handled by capabilities such as SageMaker Model Cards.

Box 1: No

• configure_azure_monitor() configures Azure Monitor and the OpenTelemetry pipeline.
• LangChain requires its own instrumentation or callback tracer, such as AzureAIOpenTelemetryTracer.
• You must pass the tracer to the LangChain execution configuration so chains, tools, prompts, and model calls become spans in Application Insights.

Box 2: Yes

text 
OTEL_SERVICE_NAME=customer-agent 
OTEL_SERVICE_NAME=invoice-agent

• A is incorrect: Flow Debugger is for debugging Salesforce Flows, not Trust Layer masking.
• B is incomplete/misleading: Requesting audit data may be part of reviewing the results, but collection and storage must first be enabled.
• C is correct: It describes the initial validation step.

• Identify the causes of delays.
• Improve its workflow and collaboration.
• Adjust tools or development practices.
• Discuss improvements during retrospectives and apply them in future sprints.

• A: An impediment log can help track issues, but merely maintaining one does not remove the impediments.
• B: Directing the team toward solutions reduces team ownership and self-organization.
• C: Adding impediments to the product backlog may be appropriate in some cases, but it does not automatically ensure they are addressed promptly.
• D: Best reflects agile leadership: empowerment, continuous improvement, and removal of impediments.

• A — Use getRecordTypeInfosByDeveloperName()

apex 
  Id rtId = Schema.SObjectType.Account 
      .getRecordTypeInfosByDeveloperName() 
      .get('Business_Account') 
      .getRecordTypeId();

• C — Query the RecordType object

apex 
  RecordType rt = [ 
      SELECT Id 
      FROM RecordType 
      WHERE SObjectType = 'Account' 
      AND Name = 'Business Account' 
      LIMIT 1 
  ];

• B: An outbound SOAP call is unnecessary and inefficient.
• D: Hardcoding an ID is not dynamic, and IDs can differ between orgs.

• Existing expected ROI: 15%
• New project ROI: 14%
• Cost of capital: 12%

• Project return = 14%
• Cost of capital = 12%
• It earns 2% more than the cost of capital, so it should increase shareholder value.

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

• File policy in Microsoft Defender for Cloud Apps: Can detect activity involving files, but it is not designed specifically to investigate risk from departing or deleted users.
• Access review policy in Microsoft Entra: Reviews whether users should retain access to resources; it does not detect historical document downloads.
• Alert policy in Microsoft Defender for Office 365: Primarily handles alerts for email and collaboration threats, not insider-risk investigations involving departed users.

• A: CEO-sponsored formal policy — demonstrates executive support, but sponsorship at one point in time may not sustain commitment.
• B: Security awareness training — primarily improves employee behavior, not senior management commitment.
• C: Periodic alignment reviews — ongoing reviews show that security remains relevant, supports business priorities, and uses resources appropriately.
• D: Senior management signoff on the strategy — useful for governance and accountability, but signoff is generally a one-time event.

• Internal audit: Reviews the organization’s own controls and processes.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A SOC 2 report is an attestation product issued by an independent auditor, but the analyst is not performing the attestation. They are reviewing it as part of vendor evaluation.

• Reconnaissance: Gathering information about the target.
• Weaponization: Creating or combining a malicious payload with a delivery method.
• Delivery: Sending the payload, such as through phishing.
• Exploitation: Triggering a vulnerability or weakness to gain execution or access.

• The vulnerability scan identifies a vulnerability.
• The administrator verifies that the vulnerability is not present.
• Therefore, the scan produced a false positive.

• True positive: A vulnerability is reported and genuinely exists.
• False negative: A vulnerability exists, but the scan fails to detect it.
• True negative: No vulnerability exists, and the scan correctly reports no issue.

• Suspended an operator who correctly refused to use unsafe equipment.
• Rewarded another operator for using the equipment despite the broken safety guard.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — This factory’s safety record is likely to be poor.

• Three DHCP scopes: Each VLAN has its own IPv4 subnet. DHCP scopes are subnet-specific, so create one scope for:

• Two DHCP relays: DHCP client discovery begins as a broadcast, and broadcasts do not cross routers or VLAN boundaries. Therefore, configure a DHCP relay on the router or Layer 3 switch interface for each client VLAN.

• NTLM: Uses Windows challenge-response authentication and does not provide the normal web-based MFA redirect flow.
• Single Sign-On: Automatically reuses existing credentials; it is intended to avoid prompting, not to support an MFA workflow.
• Transparent: Intercepts the session without redirecting the user to a separate authentication page.

• Firewall
• Intrusion prevention and detection
• Antivirus or antimalware
• Web and email filtering
• Virtual private networking (VPN)
• Sometimes content filtering and centralized reporting

• Rights issue: Raises new equity from existing shareholders. It does not increase debt or gearing, so it is least likely to breach the covenant.
• Retained earnings: Also equity finance, but the amount available may be insufficient for the required $800 million.
• Private placement of a bond: Creates additional debt and would worsen gearing, increasing the risk of breaching the covenant.
• Bank overdraft: Also debt finance, usually short-term and potentially expensive; it would still increase financial risk and gearing.

• CHAP: Uses a challenge-response exchange, so the password is not directly transmitted.
• IPsec: Provides authentication, integrity, and encryption for IP communications.
• EAP: An authentication framework that supports stronger methods, such as certificates or token-based authentication.

• A PostToolUse hook for file writes under src/api/ that runs the linter.
• A separate PostToolUse hook for API/data processing that normalizes payloads to snake_case.

• O dispositivo estar registado no Windows Autopilot;
• A atribuição de Profile1 ao grupo;
• O estado de associação ao Microsoft Entra ID e de inscrição no Intune/MDM.

• A user connects with their Google account.
• Google associates the user’s SSH key with that identity.
• IAM roles determine whether they can log in.
• Access can be tied to a specific employee for auditing.
• Removing the IAM role removes their login access.

• compute.osLogin: regular OS login access
• compute.osAdminLogin: OS login with administrative privileges, typically including sudo

text 
enable-oslogin=TRUE

apex 
for (Account updatedAccount : Trigger.new) { 
    AccountTriggerHelper.notinyxternalSystem(updatedAccount.Id); 
}

• Too many callouts: The callout occurs asynchronously in the future method, and each future transaction can perform its permitted callouts.
• Too many SOQL queries: The SOQL query is inside the future execution, not repeatedly in the trigger transaction.
• Callout from triggers not supported: Direct callouts from triggers are prohibited, but the trigger delegates the callout to asynchronous Apex, which is the correct pattern.

1. Open File Explorer.
2. Go to View ? Show ? File name extensions

1. Disable Hide extensions for known file types.
2. Rename the complete filename from Document.txt to Document.xml.
3. Confirm the extension-change warning.

• Process Builder: Automates actions based on record changes but does not create interactive forms.
• Approval Process: Routes records for approval; it is not designed to collect information through a wizard.
• Outbound Message: Sends information to an external system; it does not provide a user interface.

• Matching hashes: The software likely has not changed.
• Different hashes: The software was modified or corrupted.

• Encryption: Protects confidentiality by making data unreadable; it does not primarily detect changes.
• Baselines: Define an approved system or configuration state, but they are not the specific integrity mechanism here.
• Tokenization: Replaces sensitive data with substitute values.

• Architects design overall Splunk infrastructure and data strategy.
• Administrators manage configuration, access, and system operations.
• Knowledge Managers create and maintain knowledge objects such as data models, field extractions, and event types. They may support pivots, but they are not the primary users of them.

• True positive: The scan reports a vulnerability that really exists.
• False positive: The scan reports a vulnerability that does not exist.
• True negative: The scan correctly reports no vulnerability.
• False negative: The scan fails to detect a vulnerability that is actually present.

• Tokens: Individual units of text processed by a model, such as words, subwords, or characters.
• Models: Systems that learn patterns and generate predictions or outputs.
• Binaries: Data represented using the binary number system, not semantic representations.

Manager role

DAX 
Country[Manager] = USERPRINCIPALNAME()

• Sales
• Human Resources

CFO role

• See sales for all countries
• See no Human Resources data

• Do not restrict the Country table or Sales table.
• Apply a filter to Human Resources that always returns false, such as:

DAX 
FALSE()

• Structure requirements documents
• Draft user stories and acceptance criteria
• Create templates for functional and nonfunctional requirements
• Turn natural-language descriptions into organized documentation or implementation examples

• A: “Automatically generating detailed requirements documents” overstates Copilot’s role; it assists but does not independently determine complete requirements.
• C: /help provides guidance about Copilot features, not reliable requirements-conflict detection.
• D: Stakeholder communication and meetings remain human responsibilities.

• Technical platform interfaces: Important for integration and interoperability, but they should support—not drive—the architecture.
• Scalability of the network: Valuable as the organization grows, but a scalable solution is ineffective if it does not meet business or security needs.
• Development methodologies: Relevant to implementation, but they do not define the organization’s fundamental security requirements.

• JobTitle: User1 and User3 only
• UsageLocation: User1, User2, and User3

• For a user whose source of authority is Windows Server Active Directory, attributes such as JobTitle are synchronized to Microsoft Entra ID. You must change them in on-premises AD; editing them in Entra ID is not allowed or will be overwritten.
• UsageLocation is a cloud-managed attribute used mainly for licensing and service availability. It can be set or changed in Microsoft Entra ID, including for synchronized users.

Recommended process

1. Access each switch’s terminal.
2. Use help to identify available commands.
3. Use the MAC table command, such as:

text 
   show mac-address-table

1. Use VLAN information, such as:

text 
   show vlan

1. Use interface information, such as:

text 
   show ip interface brief

1. Record each device’s:

• A. Adjust resolution: Incorrect because an incompatible resolution usually causes no display, distortion, or an unsupported-mode message—not intermittent flickering.
• B. Swap the HDMI cable: Correct. Replacing the common, easily tested component is the appropriate troubleshooting step.
• C. Replace the projector: Incorrect because the issue also occurs with a monitor.
• D. Configure refresh rate: A mismatched refresh rate can cause visual problems, but the repeated flicker across displays points more strongly to the cable.

• Constrained VMs: VMs whose workloads are experiencing resource pressure, such as insufficient CPU or memory. They may need additional resources or optimization.
• Overprovisioned VMs: VMs allocated more CPU, memory, or storage than their workloads require. Their resources may be reclaimed or reduced.

• Underprovisioned VMs: This is not the predefined view identified for this report question.
• Zombie VMs: These are typically inactive or unused VMs and are useful for cleanup, but they are not the two views specifically intended here to identify inefficient resource allocation.

• Denial-of-service: Prevents users from accessing a service; it does not normally redirect them.
• Social engineering: Manipulates people into taking an action, such as clicking a malicious link, but does not directly alter DNS resolution.
• ARP spoofing: Associates the attacker’s MAC address with another device’s IP address on a local network. It can intercept traffic, but the described website redirection is most specifically DNS poisoning.

• B — The most significant risks are held by SQ.

• C — SQ should recognise the cars as inventory.

• F — SQ recognises revenue when LM sells a car to a third party.

• A: LM does not hold the most significant risks.
• D: LM does not recognise the cars as inventory.
• E: SQ should not recognise revenue when cars are merely delivered to LM.

• A Screen Flow can present a form that inspectors complete and submit on an Experience Cloud page.
• It can collect inspection findings, validate the input, and create or update records.
• An Autolaunched Flow has no user interface, so it cannot directly provide the form.
• A Related List only displays related records, and Record Detail is primarily for viewing or editing an existing record—not for a custom inspection submission form.

• Deterministic approve/reject results
• Strict adherence to predefined rules
• Consistent, reproducible outcomes
• Auditability and regulatory compliance

• Attack simulator — Used to run phishing and other attack simulations for user awareness training.
• Hunting — Used to proactively query security data and investigate potential threats.
• Incidents — Used to investigate and manage related alerts and active security events.