01. Which characteristic marks a value as configuration a system property should supply, rather than something written into a function's logic?
a) It stays the same in every environment and on every run of the step
b) It differs between two runs of the same step started in one environment
c) It has to be worked out from what the current run is acting on
d) It differs between the environments the same function is expected to run in
02. Several pieces of a team's custom logic run one after another because each piece ends by invoking the next itself. Inserting a piece in the middle means editing two others, and when one piece fails the pieces behind it are never reached. The team agrees to arrange the pieces as steps of a Job Template instead.
Which part of the platform then does the work their logic had been doing for itself?
a) The Job Execution record, which advances the run as steps report back
b) The Job Engine, which carries the run from one step to the next
c) The Job Template, which works through the steps it arranges once a run has started
d) The Functions Image, which starts each piece of logic in turn inside the runtime
03. An execution's status shows that the run completed, yet the change the job was meant to bring about downstream is wrong. A teammate argues that a completed status puts the fault outside the job entirely.
Which assessment of that evidence is sound?
a) Completion establishes that no step reported a failure, but it leaves open whether each step acted on the values intended
b) Completion establishes that the values supplied satisfied the template's declared parameters, placing the fault with a downstream job
c) Completion establishes that each step produced the result its mapping expected, so the consumer of that result is at fault
d) Completion establishes that the steps ran in the order the template defines, so a wrong result must come from the values
04. Which statement describes what DevOps Exchange does for an extension, and where its part ends?
a) It holds each installing organization's configuration for the extension, and applies changes to it on request
b) It produces each release from the author's project, so the author's own tooling stays out of it
c) It records what an installed extension did during a job, for the organizations that run it
d) It makes released versions available to organizations, and takes no part once one is installed
05. One Job Template is started by jobs that three teams own. Its owner saves a change to one of its steps.
How many definitions are in play for the runs those teams start next?
a) Two, until each team confirms it has taken the change
b) One for each environment the template is started in
c) One, which every team's later runs are carried out against
d) One for each team, since a caller keeps its own copy
06. A job carries out two pieces of work in a fixed order. The team now needs the second piece to be carried out before the first. Neither piece's logic changes, and both are still needed.
What does this change call for?
a) A new Functions Image, packaged with the two pieces in the required order
b) An edit to the Job Template's step sequence, which later runs then follow
c) A different set of input values at the next start, selecting the new order
d) A new release of the logic the steps invoke, built for the new order
07. The owner of a shared Job Template removed one of its steps. Three teams start jobs from that template every day. Two of them notice nothing, while the third finds that the work it runs afterward now has nothing to act on.
What best explains why the impact fell so unevenly?
a) The removal reached that team's runs first, and the others follow on their next start
b) Only that team supplies a value for the input the removed step declared
c) Only that team's work consumed the result the removed step used to produce
d) The other two teams start the template through jobs the Job Engine queues separately
08. Before a new automation is allowed to run in their organization, a review group has to satisfy itself about what the job will do and in what order on every run of it, not only on the one the builder demonstrated to them.
What should the group review?
a) The status the builder's demonstration run reported when it finished
b) The input values and the status recorded for the demonstration run
c) The execution log the builder's demonstration run wrote as it went
d) The Job Template's ordered steps and the logic each of them invokes
09. Three teams standardize on one Functions Image so their shared function meets the same runtime everywhere. Their runs still return different results.
What has the standardized image actually settled?
a) That the configuration each environment provides is fixed at one setting for all three teams
b) That every run had the same runtime, while the values and configuration each run meets differ
c) That every run returns the same result, unless one team has revised the shared logic locally
d) That the input parameters and the values supplied for them are identical across the three teams
10. Which statement describes a Job Execution once its run has finished?
a) It is a fixed record of a run that has already happened
b) It is stored on the Job Template alongside the steps that template defines
c) It is held by the Job Engine until a person marks it complete
d) It becomes the definition that later runs of that template follow