01. Six months after go-live, an audit asks the analytics team to show that warehouse content still agrees with the Fusion source. The team offers the detailed validation evidence produced at go-live sign-off, and notes that incremental uploads have carried Fusion changes into the warehouse ever since.
Why does that evidence not answer the audit?
a) It evidences the content as it stood at sign-off, while incremental uploads have changed the warehouse since, so continuing agreement needs validation that recurs.
b) It reports on warehouse content rather than on the pipelines, and continuing agreement is evidenced by showing that the scheduled pipeline runs have completed without error.
c) It was taken before the release uptake the service has had since, and evidence of load fidelity is gathered in test ahead of each release reaching production.
d) It came from a detailed comparison rather than a scheduled one, while a scheduled comparison examines the specific fields and values an audit asks about, so the depth the audit needs was never gathered.
02. One functional area needs data handled differently from what the instance-wide pipeline parameters provide. A consultant proposes hand-modifying the delivered content that serves that area so that it compensates for the difference, leaving the instance-wide settings alone.
How should the team judge that proposal?
a) Unsound, because the difference should be handled by assigning object security so only that area's users meet the content
b) Sound, if the change is confined to the single area that needs it and the other areas are left untouched
c) Unsound, because hand-modifying delivered content sits outside the supported extension points and a release can discard it
d) Sound, provided the modification is documented and reapplied whenever a release updates the delivered content
03. An organization has security automation enabled for its Fusion Data Intelligence environment. A reorganization in Fusion Applications moves several analysts to different business units, and the corresponding source-side security is updated there.
What does the implementation team expect for those analysts' access to warehouse content?
a) The team recreates the corresponding source assignments in FDI by hand so the two environments agree
b) The updated source security is propagated into FDI, so their access follows the change made in Fusion
c) The change takes effect for object security, and the row entitlements for those analysts are set separately
d) The analysts keep their previous access to warehouse content until the updated model is exported and imported through a bundle
04. Two payables specialists belong to the same FDI group and both open the delivered payables dashboard from their home pages. One sees the invoices she works on. The other sees an empty result for every prompt she selects, including prompts her colleague uses successfully. Both signed in through the corporate identity provider, and validation confirms that warehouse content agrees with the Fusion source.
What accounts for the difference?
a) The pipeline has not loaded the functional area that the second specialist's prompts depend on, so those prompts return no records
b) The group's object security covers the dashboard for one specialist and not for the other
c) The delivered dashboard was customized for one specialist's business unit and not for the other's
d) The two hold different data security assignments, so the rows each may see differ
05. Before go-live, a team met a presentation request by altering delivered content directly, and the customization served the business for several months. After a recent release the deployment shows the delivered arrangement again, and the business has raised it as an incident.
What is the durable correction?
a) Raise the request with Oracle and have the arrangement shipped in delivered content instead.
b) Reapply the change to delivered content, and schedule a check of it after every release.
c) Rebuild the change through the extension point provided for customer customizations.
d) Restore the previous state from a bundle, and repeat that restore after every release.
06. After a reporting configuration change requested by a regional finance team, one of its analysts reports that a delivered dashboard still shows only the transactions of her own business unit. She asks for a further reporting parameter change so that she can see the other units as well.
What does her request actually call for?
a) Security automation, so the entitlement held in the Fusion source is propagated into the instance and her assignment widened with it
b) A change to her data security assignment, since the rows she sees are settled there and not in presentation
c) An instance-wide pipeline parameter change, so the dashboard draws on every activated functional area
d) A further reporting parameter change, since what a dashboard puts in front of a reader is presentation behavior
07. During design, an administrator proposes to build FDI security by hand: reading the assignments that exist in Fusion Applications, entering equivalent ones in the warehouse environment, and repeating the exercise whenever the source changes. The implementation lead proposes enabling security automation instead.
What is the argument for the lead's approach?
a) Security no longer has to be configured at all, since the environment derives the entitlements on its own
b) Object and data security become a single control, so administrators maintain one setting rather than two
c) Source assignments are captured in a bundle and imported, so the exercise is repeated from a saved copy
d) Security defined in the source reaches FDI directly, so the two stay consistent and hand-entry errors are avoided
08. At a design review, a consultant proposes replacing the delivered FDI security roles with a customer-built set that mirrors them one for one, arguing that a single custom framework is tidier to document. Every access requirement on the register is already expressed by a delivered role.
How should the review respond?
a) Accept it: a custom framework is the supported way to document access on an implementation of any size
b) Accept in part: mirror the roles that govern which objects open, and leave row access to the delivered model
c) Reject it: mirroring delivered roles adds content to maintain at every release and grants nothing new
d) Reject it: customer-specific roles cannot govern delivered objects, so the delivered roles have to stay
09. Following a release, business users report that a set of measure labels they had asked for is gone from their pages, while customer-specific vocabulary elsewhere in the same model is intact. The missing labels had been applied by editing delivered content directly; the surviving vocabulary was added through the semantic model's extension point.
What should the team do so the labels do not go missing again?
a) Re-edit the delivered content and record each edit so the whole set can be reapplied after a later release
b) Reapply the labels through the semantic model's extension point, where customer vocabulary is meant to sit
c) Carry the labels in a bundle, importing it after each release so the presentation is restored
d) Raise the labels as reporting parameters so presentation settings hold them apart from the model
10. Two groups of users were onboarded to a new FDI environment on the same day, and both sign in with corporate identity without incident. Both open the same delivered dashboard. One group sees transactions on it; the other sees the dashboard render with no rows at all. The team asks whether the federation was applied inconsistently across the two populations.
What does this pattern support?
a) Both groups cleared authentication and reached the environment, so the entitlement to open the dashboard differs between them
b) Federation was applied to only one population, so authentication succeeded for a single group
c) The network path differs between the populations, so one of them reaches an empty instance
d) Both groups cleared authentication and opened the dashboard, so their row assignments differ