M3.9 module quiz
Ten questions. 80% to pass (8 of 10). Open book, unlimited retakes.
Answers are collapsed under each question. Answer first, then check.
Q1
A scoped Atlassian API token connects with:
A. Full functionality in both directions straight away
B. No functionality at all
C. Read-only access to Jira
D. Outbound ticketing working and inbound sync needing setup
Show answer
Correct: D. The inbound webhook registration uses a legacy site-based API that scoped tokens cannot call. Registering it needs a classic token and a Jira admin.
Q2
Verification of a scoped token works by:
A. Resolving the site’s cloud id and re-verifying through the Atlassian API gateway
B. Failing over to basic authentication
C. Skipping the verification step entirely when a scoped Atlassian token is used
D. Using OAuth instead of the token
Show answer
Correct: A. The resolved REST base is stored and used for every API call; the site URL is kept for human-facing deep-links, which never go through the gateway.
Q3
Ticket dedup is keyed on:
A. The recommendation id on its own, without hashing
B. The resource id on its own
C. The Jira issue key returned
D. A fingerprint of organisation, resource and rule type
Show answer
Correct: D. A recommendation id is not stable across the problem’s lifetime, so keying on it would open a second ticket every time a finding was closed and re-raised.
Q4
An assignee email that matches no Jira account results in:
A. The whole operation failing
B. A retry queue holding the pending ticket request
C. The issue being created unassigned, with a warning
D. Assignment to the bot user
Show answer
Correct: C. Failing the whole operation over a name lookup would lose the finding; creating it unassigned puts it in the queue where a human can triage.
Q5
The open_ticket policy effect’s live volume estimate exists to:
A. Predict the cost of the tickets
B. Show the ticket count of an unscoped policy before saving it
C. Rate-limit how many tickets may be created within an hour
D. Validate the policy’s conditions
Show answer
Correct: B. An unscoped policy on 412 open recommendations opens 412 tickets, once, with no undo in Jira. The estimate is the only chance to notice.
Q6
A notify and an open_ticket policy at the same scope result in:
A. Both of the effects firing at the same time against the same finding
B. A validation error on save
C. Only one firing, because the resolver returns a single most-specific winner
D. The first-created one firing
Show answer
Correct: C. Until per-lever resolution ships, the workaround is different scopes: for example notify at a broader scope and open_ticket at a narrower one.
Q7
Auto-ticketing’s publish step is:
A. Guaranteed, with an outbox
B. Best-effort; a messaging blip drops the request, visible only in a metric
C. Transactional with the write
D. Retried indefinitely in the background until the request succeeds
Show answer
Correct: B. Which makes it a convenience rather than a guarantee, so a compliance process should not assume every matching finding produced a ticket.
Q8
The loop guard prevents status ping-pong by keying on:
A. A direct timestamp comparison across both sides of the ticket link
B. A cooldown timer after each push
C. The Jira issue key on the link
D. The locale-independent neutral status category plus the last-pushed status
Show answer
Correct: D. Using the neutral category rather than display labels is what keeps it working on a Jira instance running in another language.
Q9
Reopening a Done Jira issue:
A. Reopens the recommendation
B. Does not; that direction is deferred
C. Reopens it after the next evaluation
D. Creates a new recommendation
Show answer
Correct: B. The recommender is the sole writer of recommendation status and reopens a finding when the rule fires again. Jira can request permitted transitions; it cannot substitute for detection.
Q10
Hand-made cost tickets predating the integration:
A. May be duplicated, because dedup and search-before-create both look for the fingerprint label
B. Are found and reused by the dedup path
C. Are labelled retroactively on the next sync pass, so that any duplicates collapse together
D. Block auto-ticketing for that resource
Show answer
Correct: A. A known limit rather than a defect. Route them through the integration or accept overlap during transition and close the duplicates.
What’s next
Back to Cost work in the ticket system.