Exam objectives — ASTRA Tech Sales Advisor
D1. Solution architecture, integration and operating boundaries — 14.3%
D1.1 Given a scenario, frame a scoped technical-commercial pilot from the required outcome and unknown interface capabilities.
D1.2 Given a scenario, trace the producer, consumer, integrator and business approver through a proposed flow.
D1.3 Given a scenario, choose an integration pattern that meets timing, replay and duplicate constraints.
D1.4 Given a scenario, interpret reliability test measures without hiding retries or failed records.
D1.5 Given a scenario, resolve identifier, status, timestamp and version semantics in a two-party data contract.
D1.6 Given a scenario, trace technical and approval boundaries across a candidate workflow.
D2. Cloud and solution economics — 12.5%
D2.1 Given a scenario, identify the cost meter, period, usage owner and forecast exposure behind a quote.
D2.2 Given a scenario, interpret entitlements, rights and commitment terms under changing demand.
D2.3 Given a scenario, reconcile a usage record to a defined billing line and find a mismatch.
D2.4 Given a scenario, calculate stepped or tiered charges and the cost of unused commitment.
D2.5 Given a scenario, compare scenarios without treating demand assumptions as confirmed savings.
D2.6 Given a scenario, calculate commercial economics without merging subscription and partner-service revenue.
D2.7 Given a scenario, calculate released operational capacity while separating model from realised return.
D2.8 Given a scenario, calculate the full effort model and bound the resulting commercial claim.
D3. Security, assurance and operational trust — 12.5%
D3.1 Given a scenario, identify supported least-privilege and diagnostic controls, and what remains unproven.
D3.2 Given a scenario, translate a scoped security questionnaire into claim-specific evidence requests.
D3.3 Given a scenario, assign control operation, disclosure and customer-exception decisions to their authorised owners.
D3.4 Given a scenario, interpret an assurance report within its period, tested services and exceptions.
D3.5 Given a scenario, sequence remediation, retest, customer acceptance and approved messaging.
D3.6 Given a scenario, calculate incident reporting time using the specified clock trigger and authorisation.
D3.7 Given a scenario, respond to an assurance objection without extending supplier evidence to a customer tenant.
D3.8 Given a scenario, reconcile supplier assurance with tenant controls and executed customer terms.
D4. AI value, quality and safe-use decisions — 14.3%
D4.1 Given a scenario, frame an AI-supported workflow by decision consequence, source and permitted action.
D4.2 Given a scenario, evaluate a measured model result for the intended population and operating threshold.
D4.3 Given a scenario, define allowed data, processing purpose, retention and deletion evidence.
D4.4 Given a scenario, interpret intervention metrics and choose the owner-led response to drift.
D4.5 Given a scenario, distinguish model intent, tool execution and reviewer authority in an AI control event.
D5. Technical-commercial translation and defensible recommendations — 12.5%
D5.1 Given a scenario, deliver a bounded architecture recommendation with explicit exit criteria.
D5.2 Given a scenario, compare options under complete first-year costs and nonfinancial gates.
D5.3 Given a scenario, give a conditional purchasing decision with named triggers and accountable owners.
D5.4 Given a scenario, assemble a conditional offer from cost, capability and customer acceptance evidence.
D5.5 Given a scenario, deliver a governed customer/partner handover with review and exit conditions.
D5.6 Given a scenario, sequence reversible pilot gates and the earliest evidence-backed next action.
D5.7 Given a scenario, deliver an integrated recommendation distinguishing observed, modeled and unknown outcomes.
D6. Discovery, stakeholders and decision sequencing — 12.5%
D6.1 Given a scenario, calculate and order dependent testing, security and acceptance activities.
D6.2 Given a scenario, prepare a conditional deployment handover with monitoring and reversal gates.
D6.3 Given a scenario, calculate eligible weighted pipeline without counting booked or unqualified opportunities.
D6.4 Given a scenario, frame a customer decision with technical, financial and governance constraints.
D6.5 Given a scenario, target discovery questions to the owner and the gate each answer changes.
D6.6 Given a scenario, calculate the dependency path for reversible expansion and acceptance.
D6.7 Given a scenario, frame a multi-party, multi-domain decision into a bounded customer recommendation.
D7. Partner, channel and contracting boundaries — 10.7%
D7.1 Given a scenario, define a partner motion while preserving the customer and supplier boundaries.
D7.2 Given a scenario, apply deal-registration and conflict evidence before allocating attribution.
D7.3 Given a scenario, distinguish sourced, influenced and disputed co-sell evidence.
D7.4 Given a scenario, apply capability and performance evidence to reversible enhanced-term gates.
D7.5 Given a scenario, protect customer continuity, renewal ownership and exit responsibilities.
D7.6 Given a scenario, prepare a governed channel handover with economics, owners, gaps and expiry.
D7.7 Given a scenario, resolve vendor, partner and customer authority in a proposed transaction.
D8. Evidence governance, approvals and responsible claims — 10.7%
D8.1 Given a scenario, link budget, admission and approval controls to cost and service continuity.
D8.2 Given a scenario, evaluate retention and subprocessor evidence across the actual data lifecycle.
D8.3 Given a scenario, distinguish AI assurance evidence from claims it does not establish.
D8.4 Given a scenario, assemble a conditional response across evidence, missing controls and owner actions.
D8.5 Given a scenario, assign business, data, model and execution approval decisions to the correct owners.
D8.6 Given a scenario, sequence the review, version binding and release checks for a consequential action.
D8.7 Given a scenario, decide which provider or model changes require retest before deployment.
D8.8 Given a scenario, classify observed, modeled and unestablished outcomes within one commercial claim.