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

• 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.

• 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.

• A: Concerns task scheduling and avoiding missed runs, not directly sizing the warehouse.
• B: The amount of data in a stream alone does not reliably determine compute needs; the SQL processing is what matters.
• D: A multi-cluster warehouse addresses concurrency, not the compute size needed for one task execution.

• The message came from the claimed sender (authentication)
• The message was not altered (integrity)
• The sender cannot easily deny sending it (non-repudiation)

• Attackers can send unsigned phishing emails.
• Attackers may compromise a legitimate account and send signed malicious emails.
• Users may still be tricked by a validly signed message.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records activity such as login times and resource usage.

• CIA: Confidentiality, integrity, and availability—the three core security goals.
• ACL: Access Control List, which defines permitted or denied traffic or access.
• PEM: A certificate and key encoding format, not the primary function of RADIUS.

• The application stores data on Amazon EBS volumes, so the encryption should be applied directly to those volumes.
• EBS encryption uses AWS-managed cryptographic operations and is designed to provide encryption at rest with minimal performance impact.
• The volumes are created during initial deployment, so they can be configured as encrypted when provisioned.

• B: Moving data to an encrypted S3 bucket changes the storage design and does not encrypt the EBS data the application uses.
• C: A custom encryption algorithm adds application overhead and is unnecessary.
• D: Ephemeral disks are temporary storage and can lose data when instances stop or terminate. Encrypting only the AMI’s root volume does not protect data stored elsewhere.

• AWS is responsible for the cloud infrastructure, including physical servers, hardware replacement, and firmware updates.
• For managed database services such as Amazon RDS, AWS generally manages the underlying operating system patching and infrastructure maintenance.
• The customer remains responsible for application-level software, including obtaining and paying for required application licenses.

• Operating system patches for managed databases: Typically handled by AWS.
• Hardware replacement: AWS responsibility.
• Firmware updates for physical infrastructure: AWS responsibility.

1. Open the Microsoft Entra Connect wizard.
2. Select Configure.
3. Choose Customize synchronization options.
4. Authenticate when prompted.
5. On the Domain and OU filtering page, select:

1. Complete the wizard.

• Start-ADSyncSyncCycle only starts synchronization; it does not change which OUs are included.
• Manage federation configures federation settings, which are unrelated to OU filtering.
• Add-ADSyncConnectorAttributeInclusion concerns connector attributes, not selecting additional OUs for synchronization.

1. Create Workspace2 with Lakehouse2 — F
2. Migrate the Employee table to Lakehouse2 — E
3. Assign the data engineer the Contributor role for Workspace1 — D

Why

• Sharing Lakehouse1 would not provide the required isolation.
• Viewer access would not allow writing to Customer.
• Giving Contributor access to Workspace2 would expose the sensitive table.

• Job Links ? URL ID: Mainly summarizes link performance; it is not the easiest place to retrieve individual email addresses by alias.
• Tracking Overview ? Clicks: Provides aggregate click metrics, not a targeted list for one aliased link.
• Click Activity ? Link View: Focuses on link-level reporting, but the question’s intended workflow for locating clicks tied to a specific placement/alias is Email Overlay.

• The Intune device limit restriction does not apply in the normal way; DEM enrollment supports up to 1,000 devices.
• However, the Microsoft Entra maximum number of devices per user setting can still impose a limit when the enrollment creates an Entra device object.
• Therefore, a DEM account is not automatically unlimited. The effective limit depends on the Entra device setting and the enrollment/join type.

1. insert con; ? 1
2. Database.setSavepoint(); ? 2
3. update con; ? 3
4. Database.rollback(sp_admin); ? 4

• delta.logRetentionDuration
• delta.deletedFileRetentionDuration

• delta.deletedFileRetentionDuration controls how long physically deleted or obsolete data files are retained before they become eligible for removal by VACUUM. Set it to interval 30 days.
• delta.logRetentionDuration controls how long Delta transaction-log history is retained. Set it to interval 30 days to support audits and time travel for that period.

sql 
ALTER TABLE Catalog1.Schema1.Table1 
SET TBLPROPERTIES ( 
  'delta.logRetentionDuration' = 'interval 30 days', 
  'delta.deletedFileRetentionDuration' = 'interval 30 days' 
);

• Verifies the sender’s identity using their private key.
• Confirms the transaction was not altered after signing.
• Provides evidence that the signer approved or originated the transaction.

• Digital certificates: Bind an identity to a public key, but do not themselves prove that a specific transaction was signed.
• Encrypted passwords: Protect confidentiality or authentication, but generally do not provide transaction-level nonrepudiation.
• One-time passwords: Authenticate a user for a session or transaction, but usually do not provide durable proof of who authorized the electronic record.

• B. Deploy to a SageMaker endpoint: This is needed for SageMaker-hosted models, not for a model intended to be used directly in Amazon Bedrock.
• C. Register with SageMaker Model Registry: SageMaker Model Registry is unrelated to invoking custom models in Bedrock.
• D. Grant access in Bedrock: Access permissions may be necessary, but they do not replace the required provisioned capacity.

Why A is the best fit

Why the other options are weaker

• B — Create alerts in Dynamics 365 Finance: Alerts notify users about changes; they do not calculate tax.
• C — Implement the Common Data Model: CDM standardizes data structures but does not provide tax-calculation logic.
• D — Run a Power BI report: Power BI is primarily for analysis and reporting. A report might display tax rates, but it would not normally calculate and apply tax to sales orders operationally.
• E — Write scripts and code: This could work, but it is less aligned with the requirement for a quick, cost-effective implementation because custom development requires more time and maintenance.

• Azure Cosmos DB is a globally distributed NoSQL database service. It stores and retrieves application data, but it does not provide the complete environment for building, testing, and deploying predictive analytics models.
• Azure Machine Learning is the appropriate service for this requirement. It supports creating experiments, training and testing models, and deploying them for predictions.
• Azure Machine Learning Studio provides the browser-based interface for these tasks.

• A. IDS attack signatures: Detects suspicious network activity, but is not primarily designed to scan uploaded files for malware.
• C. Load balancer: Distributes traffic among servers and improves availability; it does not inspect files for threats.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection, but its primary role is not malware scanning of uploaded documents.

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.

• Feedback form: Captures opinions, not necessarily actual behavior; users may not respond.
• Questionnaire: Relies on memory and subjective judgments about usefulness.
• Interviews: Can provide valuable qualitative insights, but a sample of users may not represent overall usage accurately.

• Default route: 0.0.0.0/0; used only when no more specific route exists.
• Network route: A route covering the destination, such as 10.10.13.0/24.
• Host route: An exact 10.10.13.10/32 entry in the routing table.
• Floating static route: A backup static route with a higher administrative distance.

• User2 is in Group1, so CA2 applies.
• CA2 targets Office 365.
• CA2 requires MFA OR an app protection policy.
• User2 has no app protection policy, but if User2 successfully completes MFA, the OR condition is satisfied.
• The device being noncompliant does not matter because CA2 does not require device compliance.
• CA1 applies only to Global Administrators. Unless User2 is also a Global Administrator, CA1 does not apply.

• WPA3: Secures wireless traffic but does not normally verify whether someone has paid.
• PSK: A shared Wi-Fi password gives access to anyone who knows it; it cannot easily validate individual receipts.
• IEEE 802.1X: Provides user/device authentication, commonly through an authentication server, but is excessive and not designed specifically for a simple receipt-based guest-access workflow.

• terraform apply
• terraform destroy

• One network address
• Two usable host addresses—one for each router
• One broadcast address

• Router A: 10.2.1.1
• Router B: 10.2.1.2

• 24 cores: Available in the Business Critical provisioned-compute configurations.
• Approximately 124 GB memory: Matches the memory capacity of the relevant Business Critical hardware configuration.
• More than 50,000 IOPS: Business Critical uses local SSD storage and provides the high I/O performance required here.
• 500 GB storage: Well within the tier’s supported capacity.

• Premium: The DTU-based Premium tier does not provide the required combination of compute, memory, and I/O characteristics.
• Hyperscale: Hyperscale is primarily intended for very large databases and independent storage scaling. It is not the best match for these specific high-memory and high-IOPS requirements.

• Floating IP must be enabled on the load-balancing rule.
• Session persistence should normally remain None.
• The health probe determines which replica should receive traffic.
• Client-IP persistence is unnecessary and can cause connections from the same client to remain associated with a backend replica longer than intended.

• Q9 — Client IP session persistence: No
• Q10 — Floating IP: Yes

• If the attachment is safe, it is released to the user.
• If malware is detected, the attachment is blocked or removed according to the policy.
• This reduces delivery delays without disabling malware scanning.

• Replace removes the original attachment and replaces it with a text file explaining that it was blocked. It does not primarily optimize delivery time.
• Block and Enable redirect blocks messages with suspicious attachments and can redirect them for review; it does not provide the required faster delivery experience.
• Monitor and Enable redirect is for observation and does not reliably block malicious attachments.

• Namespace: The namespace associated with the code where the checkpoint was set.
• Time: When the checkpoint was captured or executed.

• Exception: Exceptions are viewed through debug logs or execution results, not as the primary Checkpoints tab information.
• Debug Statement: System.debug() output belongs in the Logs tab. A checkpoint captures program state, such as variables and their values, at a specific point in execution.

• Accept terms of use
• Enter a temporary code or credentials
• Provide basic registration information

• Enterprise authentication — Authenticates organizational users, often with centralized identity services; it is not specifically designed for temporary guest access.
• Ad hoc network — A temporary device-to-device network, not an authentication process.
• WPA3 — A wireless security standard. It protects Wi-Fi access but does not provide the web-based temporary access workflow described here.

• 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.

• FUNCTION (D)
• SECURITY POLICY (E)

1. Create an inline table-valued filter predicate function. It defines which rows a user may see, often by comparing a table column with the current user identity.
2. Create a security policy that applies that function to Table1. The policy filters query results automatically.

• Deterrent control: The signs warning that people may be filmed can discourage unauthorized activity. They do not physically prevent the activity, but they may influence behavior.
• Detective control: CCTV detects or records activity so security personnel can identify incidents and investigate them later.

• Preventive: Stops an incident from occurring, such as a locked door.
• Corrective: Restores systems after an incident, such as backups.
• Directive: Instructs people what to do, such as security policies or warning instructions.
• Compensating: Provides an alternative control when the preferred control cannot be used.

• C. The agent orchestration method
• D. The average session time per agent

• Orchestration method: Classic and generative orchestration can have different processing and credit-consumption patterns. Changing the method can affect estimated operating costs.
• Average session time: Longer sessions generally involve more interaction processing, which affects projected usage, credits, and ultimately ROI.

• GPT models used: Important for technical design, but not the primary usage-estimator factor identified in this scenario.
• Average characters in a chat message: Message length alone is not the key business-use projection requested here.

1. Version 1.0.0.0 — original published version
2. Version 2.0.0.0 — newly created and published version
3. Version 3.0.0.0 — new version created when version 1 is restored

• Injection
• Broken access control
• Authentication failures
• Security misconfiguration
• Cross-site scripting

• STIX: A standardized language and format for exchanging threat intelligence.
• OVAL: Used to describe and assess system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators and intelligence about threats, but not necessarily a structured overview of common application exploitation methods.
• CVE: A catalog of individually identified, publicly disclosed vulnerabilities.

• Windows 11 Pro ? Windows 11 Enterprise
• Windows 10 Pro ? Windows 10 Enterprise

• User1 (user1@contoso.com) — This is an external guest in the Fabrikam tenant. Assuming the guest uses email one-time passcode authentication, Azure AD emails a passcode to user1@contoso.com.
• User2 (user2@outlook.com) — An Outlook.com address can authenticate with a Microsoft account, so Azure AD uses that account’s authentication rather than sending an email OTP. The fact that User2 has never accessed Fabrikam resources does not by itself trigger OTP.
• User3 (user3@fabrikam.com) — This is an internal Fabrikam user, so the user signs in with the organization’s normal credentials and does not receive a guest OTP.

Correct sequence

1. Merge Sales_Region with Sales_Manager using an inner join

1. Merge Region_Manager with Manager using an inner join

1. Merge Sales_Region and Region_Manager using a right join as a new query

• IKE (Internet Key Exchange) negotiates the IPsec security association, including:

• ESP (Encapsulating Security Payload) protects the data after negotiation by providing encryption and optionally authentication.
• AH provides authentication and integrity but does not encrypt traffic.
• TLS is used for protocols such as HTTPS, not for negotiating IPsec parameters.

• MFA: Protects sign-in and authentication.
• Azure Key Vault: Protects deployment secrets and credentials.
• Answer: No (B).

• Install unauthorized or unsupported software
• Access features blocked by the manufacturer or operating system
• Customize system behavior beyond normal settings

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• Un AG puede tener réplicas en Windows y Linux desde SQL Server 2017; por tanto, una réplica Windows y otra Linux es posible.
• Sin embargo, las réplicas de un AG deben utilizar normalmente la misma versión principal de SQL Server. Una instancia SQL Server 2017 no puede tener directamente una réplica secundaria SQL Server 2019 como configuración normal y permanente.
• En tu escenario, SQL Server 2017 en Windows y SQL Server 2019 en Linux no se pueden añadir directamente como réplicas equivalentes de AG1. Primero habría que realizar un proceso de actualización/migración compatible, por ejemplo mediante una actualización gradual o una tecnología de migración como log shipping o distributed availability groups, según el diseño.

• Tipo de clúster y mecanismo de quorum.
• Failover normalmente manual en configuraciones multiplataforma.
• Edición y características compatibles.
• Configuración de endpoints y permisos.
• Limitaciones específicas de SQL Server en Linux.

• Ramen is a Linux worm associated with Red Hat Linux 6.2 and 7.0 systems.
• It spreads by scanning randomly generated IP addresses using tools such as synscan.
• It exploits vulnerable network services, including web-related services, and may leave malicious files or altered web content.
• The tar.gz file is also a clue because it is a common Linux archive/package format.

• Code Red: Primarily targeted Microsoft IIS servers running Windows.
• LoveLetter: Spread mainly through email attachments.
• Nimda: A Windows-based worm that spread through email, web servers, and network shares.