Technology
ServiceNow CAD: ACLs in ServiceNow: Security Starts With the Data Model
Access controls in ServiceNow are often discussed as a security feature added after an application exists, but the strongest designs start much earlier. The table hierarchy, record ownership, reference structure, and field sensitivity determine what an ACL can express cleanly. The current ServiceNow CAD exam gives security and restricting access substantial weight because a ServiceNow application developer is expected to protect data at the platform boundary, not merely hide fields on a form. Home/ServiceNow/ServiceNow CAD: ACLs in ServiceNow: Security Starts With the Data ModelServiceNowPublished October 3, 2026On this pageStart…
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…
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…
Google Professional Cloud Architect: Designing for Regional Failure
A system that survives a server failure can still fail completely when an entire region is unavailable. Regional resilience starts by accepting that a region is a failure domain, then deciding which user journeys, data, and control paths must continue somewhere else. That is a different problem from simply placing two virtual machines in separate zones. Home/Cloud & Architecture/Google Professional Cloud Architect: Designing for Regional FailureCloud & ArchitecturePublished October 3, 2026On this pageTreat zones and regions as different failure boundariesStart with RTO and RPO, not a topology diagramSeparate stateless failover…
Google Professional Cloud Architect: Cloud Storage Classes
Cloud Storage class decisions are easy to reduce to a price table: Standard for active data, Nearline for less frequent access, Coldline for colder data, Archive for the longest retention. That summary is useful, but it is not enough to design a storage lifecycle. The real decision includes access frequency, retrieval behavior, minimum storage duration, retention rules, recovery needs, compliance, and the cost of moving or deleting objects early. Home/Google/Google Professional Cloud Architect: Cloud Storage ClassesGooglePublished October 3, 2026On this pageClassify data by access pattern and consequenceUnderstand the economics behind…
Google Professional Cloud Architect: Pub/Sub and Event-Driven Systems
Event-driven architecture is attractive because producers can publish facts without knowing which consumers will use them. That decoupling can make systems easier to evolve, scale, and integrate, but only if the design accepts the realities of distributed messaging: retries, duplicates, delayed processing, ordering limits, schema evolution, and partial failure. Home/Cloud & Architecture/Google Professional Cloud Architect: Pub/Sub and Event-Driven SystemsCloud & ArchitecturePublished October 3, 2026On this pageUse events to separate responsibility, not to avoid APIsDesign consumers for at-least-once deliveryOrdering should be scoped to the business requirementExactly-once is a tool, not permission…
Google Professional Cloud Architect: Cloud SQL, Spanner, or Firestore?
Cloud database decisions often go wrong when teams begin with product reputation rather than workload behavior. Cloud SQL, Spanner, and Firestore can all store application data, but they solve different problems. The choice should follow transaction semantics, access patterns, scale, consistency, schema shape, regional requirements, and operating model. Home/Google/Google Professional Cloud Architect: Cloud SQL, Spanner, or Firestore?GooglePublished October 3, 2026On this pageCloud SQL is often the right answer when ordinary relational behavior is enoughSpanner is for relational correctness at much larger distributed scaleFirestore fits document-oriented application stateTransaction boundaries reveal the…
Google Professional Cloud Architect: Landing Zones Before Growth
A landing zone is the foundation that determines how new cloud projects inherit identity, network, security, billing, logging, and policy decisions. Its purpose is not to make every workload identical. It is to make safe, supportable defaults available before hundreds of teams create their own incompatible versions. Home/Cloud & Architecture/Google Professional Cloud Architect: Landing Zones Before GrowthCloud & ArchitecturePublished October 3, 2026On this pageResource hierarchy is an operating modelUse organization policy for preventive guardrailsIdentity design should minimize standing privilegeNetwork foundations should enable teams without erasing boundariesCentralize the evidence needed to…
Google Professional Cloud Architect: Observability Without Telemetry Noise
Observability becomes expensive and noisy when teams collect everything without deciding what they need to know. Logs, metrics, and traces are useful because they answer different questions, but a platform that emits millions of signals can still leave operators unable to explain why users are failing. Home/Cloud & Architecture/Google Professional Cloud Architect: Observability Without Telemetry NoiseCloud & ArchitecturePublished October 3, 2026On this pageStart with user-facing service objectivesLogs explain events, but volume needs purposeTraces show where distributed latency accumulatesAlert on symptoms that require actionUse SLOs to turn telemetry into prioritiesControl telemetry…
Google Professional Cloud Architect: Identity-Aware Proxy for Internal Apps
Traditional internal applications often inherit a simple security assumption: if a user can reach the private network, the application can trust the connection. Remote work, cloud hosting, contractors, unmanaged devices, and multi-environment access make that assumption increasingly weak. Identity-Aware Proxy changes the control point by evaluating identity and authorization at the application access layer instead of granting broad network reach. Home/Cloud & Architecture/Google Professional Cloud Architect: Identity-Aware Proxy for Internal AppsCloud & ArchitecturePublished October 3, 2026On this pageMove the trust decision closer to the applicationUse group-based access instead of individual…
Google Professional Cloud Architect: Rehost, Replatform, or Redesign?
Migration strategy is often presented as a set of labels: rehost, replatform, refactor, re-architect, replace, or retire. Those labels are useful shorthand, but they are not decisions by themselves. The right path depends on business deadlines, technical debt, dependencies, licensing, data gravity, operational skill, resilience requirements, and how much change the organization can absorb at once. Home/Cloud & Architecture/Google Professional Cloud Architect: Rehost, Replatform, or Redesign?Cloud & ArchitecturePublished October 3, 2026On this pageRehost when speed and compatibility dominateReplatform when managed services remove real operational burdenRedesign when the current architecture blocks…
Google Professional Cloud Architect: Reading Architecture Case Studies
Architecture case studies are difficult because almost every technology mentioned can be made to work. The task is to identify which requirements are non-negotiable, which constraints are merely preferences, where risk is concentrated, and which design best satisfies the whole situation rather than one isolated feature. Home/Cloud & Architecture/Google Professional Cloud Architect: Reading Architecture Case StudiesCloud & ArchitecturePublished October 3, 2026On this pageRead the business objective before the technical inventoryMark hard constraints separately from preferencesTranslate symptoms into architectural requirementsFind the decision domain before selecting a productUse elimination before optimizationRead for…
Google Professional Cloud Architect: FinOps for Architects
Cloud cost is often treated as an operations problem that begins after a system is deployed. By then, many of the largest cost drivers are already locked in: region count, replication model, data movement, database choice, compute platform, retention, tenancy design, observability volume, and whether the application can scale down when demand disappears. Home/Cloud & Architecture/Google Professional Cloud Architect: FinOps for ArchitectsCloud & ArchitecturePublished October 3, 2026On this pageArchitecture creates the cost curveSeparate utilization decisions from pricing decisionsMake cost attributable to owners and productsData transfer can dominate distributed designsManaged services…
CompTIA 220-1201: Wi-Fi Problems Are Often Radio Problems
When wireless performance collapses, the router is usually the first device blamed. Users reboot it, replace it, or move to a faster internet plan. Sometimes that works. Often the real problem is not routing at all. It is radio behavior: weak signal, interference, channel contention, poor access-point placement, client limitations, or too many devices competing for airtime. Home/CompTIA/CompTIA 220-1201: Wi-Fi Problems Are Often Radio ProblemsCompTIAPublished October 3, 2026On this pageSignal strength is not the same thing as usable capacity2.4 GHz, 5 GHz, and 6 GHz involve different trade-offsChannel contention behaves…