Practice Exams:

IT Operations & Service Management

ServiceNow CIS-DF: Fixing Duplicate CIs in ServiceNow

Duplicate configuration items are rarely just a cleanup problem. They are evidence that one or more ingestion paths disagree about identity. Two records may represent the same server because Discovery and a connector used different identifiers, a transform bypassed IRE, a hostname changed, a cloud resource was recreated, or an identification rule was too weak. Manually merging the records fixes today’s symptom; fixing the identity architecture stops tomorrow’s duplicates. Home/ServiceNow/ServiceNow CIS-DF: Fixing Duplicate CIs in ServiceNowServiceNowPublished October 7, 2026On this pageConfirm that the records are truly duplicatesFind the ingestion paths…

Read More

ServiceNow CIS-DF: Discovery Data Into a Healthy CMDB

ServiceNow Discovery is useful only when the data it collects improves the CMDB instead of creating a second stream of noisy infrastructure records. Discovery can scan IP ranges, use MID Servers and credentials, classify devices, run patterns or probes, identify configuration items, and update the CMDB on a schedule. The engineering challenge is making sure those observations land in the correct classes, match existing CIs, respect source authority, create useful relationships, and age out correctly when the underlying environment changes. Home/ServiceNow/ServiceNow CIS-DF: Discovery Data Into a Healthy CMDBServiceNowPublished October 7,…

Read More

ServiceNow CIS-DF: CSDM 5 in Practical Terms

ServiceNow’s Common Service Data Model is a prescriptive model for organizing service-related data so the Now Platform can use the same definitions across products and workflows. CSDM 5 extends that model and clarifies how business capabilities, business applications, services, service offerings, service instances/application services, and infrastructure configuration items relate to one another. It is not a separate product or SKU, and it is not an implementation process that replaces configuration management. On this page Think of CSDM as shared language Use business and technical services deliberately Follow current prescribed relationships…

Read More

ServiceNow CIS-DF: CMDB Health Metrics That Matter

CMDB health should answer whether ServiceNow contains enough accurate, governed, and relationally useful configuration data to support operations. A single “health score” can be convenient, but teams need to understand the components behind that score and which defects actually affect incident, change, service mapping, automation, and reporting. On this page Use Completeness for fields teams actually need Check compliance and relationship quality Set thresholds by class importance Watch trend and recurrence Use the dashboard as a starting point Diagnose correctness, compliance and relationship gaps Route meaningful remediation and measure progress…

Read More

ServiceNow CIS-DF: CMDB Governance Across Teams

CMDB governance fails when everyone can write data but nobody owns the meaning, quality, or lifecycle of what was written. ServiceNow CMDB spans infrastructure, applications, cloud resources, service modeling, ITSM, ITOM, asset management, security, enterprise architecture, and reporting. No single team has enough context to govern all of those domains alone. On this page Define the platform steward Assign source-system ownership Govern relationships separately Make health metrics actionable Measure governance by trust and throughput Assign decision rights and govern sensitive CMDB access Prioritize governance by critical service risk Maintain stewardship…

Read More

ServiceNow CIS-DF: CMDB Data Models That Stay Clean

A clean ServiceNow CMDB begins with a disciplined data model: configuration items belong in the right classes, each class has a clear purpose and identifiers, authoritative sources are known, duplicate creation is controlled, relationships are consistent, and lifecycle rules remove records that no longer represent the environment. Cleaning data after every import is expensive; designing the model so bad data is harder to create is more scalable. Home/ServiceNow/ServiceNow CIS-DF: CMDB Data Models That Stay CleanServiceNowPublished October 7, 2026On this pageUse the existing class hierarchy firstUse IRE for identificationKeep identifiers stableDesign…

Read More

ServiceNow CIS-DF: CI Relationships That Support Operations

Configuration items become operationally useful when ServiceNow can show how they depend on one another and which services they support. A server record with perfect CPU, owner, and serial-number data can still be almost useless during an outage if nobody knows which application service depends on it. CI relationships turn the CMDB from an inventory into a model that can support impact analysis, change planning, troubleshooting, service health, and automation. Home/ServiceNow/ServiceNow CIS-DF: CI Relationships That Support OperationsServiceNowPublished October 7, 2026On this pageModel relationships that answer operational questionsPrefer platform-standard relationshipsConnect infrastructure…

Read More

ServiceNow Platform Engineering

ServiceNow Platform Engineering is the discipline of designing the Now Platform so data, configuration, services, integrations, automation, security, and operations remain maintainable as the enterprise grows. The platform is not only a collection of workflows. It is a shared data and execution environment whose value depends on stable models, trusted configuration data, clear ownership, reusable standards, and change practices that let many teams build without fragmenting the platform. For the Data Foundations cluster, the Configuration Management Database is one of the most important shared platform services. A trustworthy CMDB needs…

Read More

Microsoft Platform Operations

Microsoft platform operations sits where application delivery, endpoint management, low-code governance, collaboration, and enterprise identity meet. Azure DevOps and GitHub move software. Intune and Entra evaluate endpoint trust. Power Platform environments host business applications and automation. Teams becomes a collaboration surface backed by Microsoft 365 Groups, SharePoint, identity, and compliance controls. Operating these services at scale requires a consistent way to manage change, ownership, security, lifecycle, and evidence. Home/Microsoft/Microsoft Platform OperationsMicrosoftPublished October 7, 2026On this pageBuild governed delivery instead of custom pipelines everywhereTreat Power Platform as a software estateMake solutions…

Read More

IT Support with CompTIA

IT Support with CompTIA is the practical layer where users, endpoints, operating systems, networks, security controls, applications, hardware, and business procedures meet. A support technician does more than replace parts or follow a script. The job is to identify the problem, preserve user productivity and data, apply safe changes, communicate clearly, understand when security or infrastructure specialists need to take over, and document enough evidence that the next technician does not start from zero. Home/IT Operations & Service Management/IT Support with CompTIAIT Operations & Service ManagementPublished October 7, 2026On this…

Read More

IT Operations & Project Delivery

IT operations and project delivery meet wherever a technical change has to become a dependable business outcome. Operations teams care about stability, supportability, access, monitoring, recovery, and recurring workload. Project teams care about scope, schedule, dependencies, risk, stakeholders, acceptance, and the transition from temporary work into normal service. When those perspectives are separated, projects can finish “on time” while leaving support teams with unclear ownership, weak documentation, unresolved risk, or systems that are difficult to operate. This hub connects practical delivery skills around CompTIA Project+, IT service management, and operational…

Read More

Fortinet FCSS_EFW_AD-7.6: Troubleshooting Complex FortiGate Environments

  Complex FortiGate environments punish random troubleshooting. A user reports that an application is slow, a tunnel is up but traffic fails, one branch works while another does not, or sessions break only after failover. It is tempting to change policies, routes, and SD-WAN settings until the symptom disappears. That approach destroys evidence and often replaces one problem with another. Home/Fortinet/Fortinet FCSS_EFW_AD-7.6: Troubleshooting Complex FortiGate EnvironmentsFortinetPublished October 3, 2026On this pageWrite the expected packet path before collecting outputSeparate the control plane from the data planeRouting lookup comes before firewall policyThen…

Read More

Palo Alto Networks NETSEC-PRO: Traffic Troubleshooting: Session to Policy

Firewall troubleshooting becomes slow when engineers jump directly to the rulebase and start changing policy until traffic works. A Palo Alto Networks firewall is stateful: packets belong to sessions, routing and zones shape the path, NAT can change addresses, application identification can evolve, and security policy applies to the session. The fastest diagnosis usually comes from reconstructing that path in order rather than guessing at one configuration page. Home/Palo Alto Networks/Palo Alto Networks NETSEC-PRO: Traffic Troubleshooting: Session to PolicyPalo Alto NetworksPublished October 3, 2026On this pageStart with a precise five-tuple…

Read More

CompTIA N10-009: Layered Connectivity Troubleshooting That Actually Works

Connectivity troubleshooting becomes slow when every possible cause is investigated at once. The layered method works because it imposes order. Instead of jumping immediately to DNS, firewalls, routing, wireless, or the application, the technician starts with the symptom and asks which lower dependency must be true before the next layer can work. Each test narrows the fault domain. The method is especially important when multiple layers fail at once: a wrong network mask may imitate a routing defect, and successful transport may still coexist with unusable DNS settings. Home/CompTIA/CompTIA N10-009:…

Read More

Microsoft MD-102: Troubleshooting Intune From Assignment to Device Check-In

Intune troubleshooting becomes much faster when administrators stop treating a failed setting as one event. A policy must exist, target the right user or device, be applicable to that platform, reach the endpoint, process successfully, change local state, and report the result back to the service. A failure at any one of those stages can produce the same user complaint: “the policy did not apply.” Home/Microsoft/Microsoft MD-102: Troubleshooting Intune From Assignment to Device Check-InMicrosoftPublished October 3, 2026On this pageBegin by proving that the object is the device you think it…

Read More