Certifications
ServiceNow CAD: Building Scoped Applications That Can Survive an Upgrade
A custom ServiceNow application is successful only if it can keep working as the platform, its dependencies, and the business process around it change. The ServiceNow CAD exam includes managing applications because development does not end at the first production deployment. A ServiceNow developer has to make choices about scope, configuration, source, testing, and dependencies that determine whether the application survives future upgrades without becoming a repair project. Home/ServiceNow/ServiceNow CAD: Building Scoped Applications That Can Survive an UpgradeServiceNowPublished October 3, 2026On this pageApplication scope is a maintenance boundary, not…
ServiceNow CAD: IntegrationHub and REST API Boundaries
An integration is a boundary between systems, and the quality of that boundary matters more than the convenience of the first successful API call. ServiceNow’s CAD exam includes working with external data because application developers on the ServiceNow certification path need to design integrations that remain understandable when credentials rotate, payloads change, calls time out, or the remote service becomes unavailable. IntegrationHub, REST APIs, import mechanisms, and custom scripting are tools for different parts of the same problem. The architectural work is defining the contract: which system owns each…
ServiceNow CAD: Testing Applications Before Users Do
Users should not be the first people to discover that a ServiceNow application no longer works. Testing is part of development, not a phase that begins after the application is considered finished. The ServiceNow CAD exam includes managing applications because a developer on the ServiceNow certification path has to verify behavior across changes, roles, integrations, and upgrades—not simply prove that one form worked once in a development instance. Home/ServiceNow/ServiceNow CAD: Testing Applications Before Users DoServiceNowPublished October 3, 2026On this pageStart with business-critical behavior, not the easiest clicks to automateDesign…
ServiceNow CAD: GlideRecord Queries and Performance
A ServiceNow application can feel perfectly fast in development and still become painful in production because a query that looks harmless is executed against a much larger table, inside a more frequently triggered rule, or once for every record in another loop. That is why performance work belongs in application design, not only in post-launch troubleshooting. The ServiceNow CAD exam expects developers to understand server-side logic and data access, while ServiceNow certifications reinforce that platform behavior is inseparable from the data model underneath it. Home/ServiceNow/ServiceNow CAD: GlideRecord Queries and…
ServiceNow CAD: Events, Notifications, and Async Work
ServiceNow applications become easier to operate when a user transaction does only the work that must finish before the user receives a response. Everything else should be evaluated for event-driven, asynchronous, scheduled, or flow-based execution. The ServiceNow CAD exam has long treated events and automation as core developer knowledge, and ServiceNow certifications reinforce the same point operationally: automation architecture affects reliability, latency, and maintainability. Home/ServiceNow/ServiceNow CAD: Events, Notifications, and Async WorkServiceNowPublished October 3, 2026On this pageKeep the synchronous transaction smallAn event should describe what happenedNotifications should consume state, not…
ServiceNow CAD: From Business Requirement to Maintainable App
The hardest part of a ServiceNow application is often not writing the script or drawing the flow. It is translating a vague business request into a model that remains understandable after the first release. The ServiceNow CAD exam tests application design because platform development starts with decisions about data, users, scope, security, and process. That architectural discipline also matters across ServiceNow certifications, because platform features remain useful only when the underlying model can survive real organizational change. Home/ServiceNow/ServiceNow CAD: From Business Requirement to Maintainable AppServiceNowPublished October 3, 2026On this…
ServiceNow CAD: Debugging ServiceNow Logic Without Guessing
Guessing is an expensive debugging strategy. It encourages developers to change several things at once, retest manually, and stop when the symptom disappears without understanding the cause. ServiceNow provides better options: session debugging, the Script Debugger, Session Log, Script Tracer, browser developer tools, application-scope diagnostics, and targeted test techniques. The ServiceNow CAD exam expects developers to write, test, and debug scripts, while ServiceNow certifications reward a methodical approach because production issues rarely respect the boundary of one script file. Home/ServiceNow/ServiceNow CAD: Debugging ServiceNow Logic Without GuessingServiceNowPublished October 3, 2026On…
Microsoft AB-620: Give an AI Agent a Job Before More Tools
An AI agent does not become useful because it has access to more tools. It becomes useful when it has a clear responsibility, knows which requests belong to that responsibility, and can complete those requests within explicit boundaries. That design work appears directly in the current Microsoft AB-620 exam, which emphasizes planning agent solutions before extending them, and the same architecture discipline appears across Microsoft certifications that cover production AI and application delivery. Home/Microsoft/Microsoft AB-620: Give an AI Agent a Job Before More ToolsMicrosoftPublished October 3, 2026On this pageDefine the…
Microsoft AB-620: Copilot Studio Topics vs. Agent Reasoning
Copilot Studio topics and agent reasoning solve different problems. A topic is an authored unit of conversation or process logic; generative orchestration is the planning layer that decides which topics, tools, knowledge sources, or connected agents should be used for a request. The current Microsoft AB-620 exam reflects that distinction by testing both topic configuration and generative orchestration, while Microsoft certifications increasingly expect builders to combine deterministic components with model-driven planning. Home/Microsoft/Microsoft AB-620: Copilot Studio Topics vs. Agent ReasoningMicrosoftPublished October 3, 2026On this pageA topic is an executable building blockReasoning…
Microsoft AB-620: Designing Agent Actions That Fail Safely
Giving an AI agent permission to act changes the design problem. An answer can be corrected; an action can create a ticket, send a message, update a customer record, start a workflow, or modify data before anyone notices the mistake. The current Microsoft AB-620 exam explicitly covers agent flows, tools, connectors, APIs, identity strategy, security, governance, and human-in-the-loop patterns. Those same controls also matter across Microsoft certifications that cover secure application and AI solution delivery. Home/Microsoft/Microsoft AB-620: Designing Agent Actions That Fail SafelyMicrosoftPublished October 3, 2026On this pageStart with the…
Microsoft AB-620: Knowledge Grounding
An agent should not treat every piece of information as something it “knows.” Some facts belong in instructions because they define behavior. Some belong in enterprise knowledge sources because they change over time. Some must be retrieved from live systems because they are specific to the user or current transaction. The current Microsoft AB-620 exam tests enterprise knowledge sources, Azure AI Search, generative answers, custom knowledge, tools, and integration patterns, making grounding a practical design skill across Microsoft certifications focused on modern AI solutions. Home/Microsoft/Microsoft AB-620: Knowledge GroundingMicrosoftPublished October 3,…
Microsoft AB-620: Coordination Problems in Multi-Agent Systems
Multi-agent systems promise specialization: one agent understands finance, another knows HR, another performs technical diagnostics, and a coordinator routes work between them. The architecture can be powerful, but every new agent introduces another boundary, identity, contract, failure mode, and routing decision. The current Microsoft AB-620 exam explicitly includes multi-agent solutions, connected agents, Foundry agents, Fabric data agents, and the Agent2Agent protocol, making coordination a core skill across Microsoft certifications that address agentic solution design. Home/Microsoft/Microsoft AB-620: Coordination Problems in Multi-Agent SystemsMicrosoftPublished October 3, 2026On this pageSplit agents by stable responsibility,…
Microsoft AB-620: Identity and Permissions Are Part of Agent Design
Identity and permissions are not deployment details for an AI agent. They determine what the agent can see, which user it represents, which tools it may call, and what the backend will allow when a request becomes an action. The current Microsoft AB-620 exam includes identity strategy, security, governance, connectors, APIs, and enterprise integration, so authorization is a core design concern across Microsoft certifications covering enterprise AI and application security. Home/Microsoft/Microsoft AB-620: Identity and Permissions Are Part of Agent DesignMicrosoftPublished October 3, 2026On this pageSeparate the user’s identity from the…
Databricks Generative AI Engineer Associate: Production Prompt Engineering
Prompt engineering starts as language work, but production changes its nature. Once a prompt controls a customer workflow, an internal agent, or a retrieval pipeline, edits become behavioral changes to a software system. The current Databricks Generative AI Engineer Associate exam and the broader Generative AI Engineer Associate certification reflect that shift by testing prompt design alongside version control, evaluation, CI/CD, governance, and monitoring rather than treating prompts as isolated strings. Home/Databricks/Databricks Generative AI Engineer Associate: Production Prompt EngineeringDatabricksPublished October 3, 2026On this pageA production prompt has a contract…
Cisco 350-701: DNS Security Belongs in the Threat Model
Home/Cisco/Cisco 350-701: DNS Security Belongs in the Threat ModelCiscoPublished October 3, 2026On this pageDNS creates a security decision before most application traffic beginsResolution reliability is part of the security designDomain blocking works best as a risk-reduction layerDNS tunneling changes the protocol from directory service to transportEncrypted DNS changes visibility, not the need for policyCache poisoning and redirection attack trust in the answerDNS logs become more valuable when identity and endpoint context are addedResponse should address the compromised system, not only the requested namePut DNS into architecture reviews and threat models…