Author Archives: Allen Rodriguez
The 2026 PMP refresh changes the center of gravity of the exam. Project managers still need to understand teams, planning, delivery, risk, quality, and change, but the current blueprint asks more often whether those activities produce an outcome the organization can defend. That is a different question from whether a project followed a familiar process […]
Cost optimization is easiest to misunderstand when it is treated as a hunt for the cheapest service. Architecture cost is the result of workload shape, reliability targets, performance, licensing, data movement, operational effort, security requirements, and the reversibility of the design. A lower monthly resource bill can be more expensive overall if it creates fragile […]
Resiliency is often discussed as a collection of patterns: retries, queues, replicas, availability zones, multiple regions, health probes, and circuit breakers. Those mechanisms matter, but they do not create a resilient application by themselves. Reliability emerges from how the components, dependencies, data, and operational procedures behave together when something is degraded. The current AZ-305 exam […]
Data-platform decisions are usually made before every requirement is known. Teams know the broad workload, expected users, and business goals, but future scale, query patterns, integration volume, consistency needs, and governance pressure are still changing. That makes architecture less like selecting the “best database” and more like managing uncertainty. The current AZ-305 exam includes data […]
Business continuity is not the same as making every component highly available. A system can survive a server failure and still be unprepared for a regional outage, ransomware event, identity failure, corrupted deployment, or operator mistake. Recovery architecture begins with the business outcome that must survive, then works backward into failure domains, data protection, traffic […]
Identity architecture can look correct in a diagram and still fail in practice. A tenant can have multifactor authentication, Conditional Access, privileged-role controls, and neatly assigned groups while a service principal holds excessive permissions, an emergency account bypasses normal controls, a cross-tenant trust is broader than expected, or administrators use the same identity for ordinary […]
Hub-and-spoke networking is attractive because the first diagram is clean: shared connectivity and controls sit in a hub, application networks live in spokes, and peering connects the pieces. Problems usually appear later, when the environment adds regions, subscriptions, overlapping ownership, private endpoints, inspection requirements, hybrid routes, and hundreds of spokes. The current AZ-305 exam expects […]
Azure management groups and subscriptions look simple when an environment is small. A few subscriptions can be organized by naming convention and managed by people who know the history. At scale, those informal rules stop working. Governance inheritance, access boundaries, cost ownership, quotas, policy scope, deployment automation, and organizational change all depend on how the […]
An Azure landing zone is easy to mistake for a deployment template. The more useful view is that it is an operating architecture: a way to create repeatable boundaries for governance, identity, networking, security, management, and workload ownership as Azure usage grows. The current AZ-305 exam reflects that broader architectural responsibility by assessing design across […]
ServiceNow implementations often begin with a tempting question: which module, workflow, integration, or automation should we configure first? The current Data Foundations certification shifts that starting point. The CIS-DF (CMDB and CSDM) blueprint is centered on designing, implementing, and operationalizing a CMDB that supports the Common Service Data Model. That framing makes data structure and […]
Architecture decisions built on CMDB data are only as defensible as the data assumptions underneath them. A dashboard can look precise while combining stale configuration items, duplicated identities, weak relationships, and attributes written by sources with conflicting authority. The result is dangerous because the presentation looks more certain than the evidence really is. The current […]
CMDB quality programs often fail in one of two ways. Some rely on dashboards that show scores but do not change behavior. Others rely on periodic human cleanup without a consistent way to measure whether quality is improving. ServiceNow provides two complementary mechanisms—CMDB Health and Data Certification—that become valuable when they are connected to ownership, […]
When multiple tools describe the same infrastructure, the CMDB has two different problems to solve. First, it must decide whether an incoming record refers to a CI that already exists. Second, once the correct CI is found, it must decide whether the incoming source is allowed to update the attributes it supplied. ServiceNow separates those […]
A CMDB is shared infrastructure for decision-making. Incident teams use it to understand impact. Change teams use it to evaluate risk. Security teams use it to understand exposure. Service owners use it to trace dependencies. Architects and application teams use it to explain what exists. Because so many groups consume the data, ownership cannot be […]
A CMDB design can look elegant when it contains a few thousand records and become painful when the organization adds cloud services, acquisitions, multiple discovery sources, new teams, and years of customization. The scaling problem is rarely storage capacity. It is semantic capacity: can the model keep representing different technologies and ownership structures without losing […]
